Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #8447 > unrolled thread

Re: plans for eclipse luna in debian

Back to article view | Back to linux.debian.maint.java

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-09 18:50 +0200
    Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-10-09 19:30 +0200
      Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-10 09:00 +0200
        Re: plans for eclipse luna in debian Emmanuel Bourg <ebourg@apache.org> - 2015-10-10 09:10 +0200
        Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-10-10 11:40 +0200
          Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-13 09:50 +0200
            Re: plans for eclipse luna in debian Emmanuel Bourg <ebourg@apache.org> - 2015-10-13 09:50 +0200
      Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-17 15:10 +0200
        Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-10-17 17:10 +0200
          Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-10-18 17:50 +0200
            Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-20 13:00 +0200
              Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-10-20 19:10 +0200
                Re: plans for eclipse luna in debian Pascal Rapicault <pascal@rapicorp.com> - 2015-10-21 03:50 +0200
                  Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-25 22:20 +0100
                    Re: plans for eclipse luna in debian Pascal Rapicault <pascal@rapicorp.com> - 2015-10-27 01:30 +0100
                Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-23 21:00 +0200
                Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-31 13:30 +0100
                  Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2015-10-31 15:50 +0100
                    Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-10-31 16:40 +0100
                      Re: plans for eclipse luna in debian Pascal Rapicault <pascal@rapicorp.com> - 2015-11-02 08:50 +0100
                  Re: plans for eclipse luna in debian Michael Tautschnig <mt@debian.org> - 2015-10-31 15:50 +0100
                Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-11-10 20:00 +0100
                  Re: plans for eclipse luna in debian Mikołaj Izdebski <zurgunt@gmail.com> - 2015-11-10 23:30 +0100
                    Re: plans for eclipse luna in debian Emmanuel Bourg <ebourg@apache.org> - 2015-11-11 00:40 +0100
                      Re: plans for eclipse luna in debian Mikołaj Izdebski <zurgunt@gmail.com> - 2015-11-12 01:10 +0100
                    Re: plans for eclipse luna in debian Markus Koschany <apo@gambaru.de> - 2015-11-13 19:00 +0100
                  Re: plans for eclipse luna in debian Markus Koschany <apo@debian.org> - 2015-12-13 22:20 +0100
                    Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-01-07 13:20 +0100
                      Re: plans for eclipse luna in debian Markus Koschany <apo@debian.org> - 2016-01-07 13:50 +0100
                        Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-01-07 15:40 +0100
                          Re: plans for eclipse luna in debian Markus Koschany <apo@debian.org> - 2016-01-07 16:30 +0100
                            Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-01-16 08:30 +0100
                              Re: plans for eclipse luna in debian Christopher Hoskin <christopher.hoskin@gmail.com> - 2016-02-16 10:20 +0100
                                Re: plans for eclipse luna in debian Thorsten Glaser <t.glaser@tarent.de> - 2016-02-16 10:20 +0100
                                  Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-02-16 18:40 +0100
                                    Re: plans for eclipse luna in debian Thorsten Glaser <t.glaser@tarent.de> - 2016-02-16 21:00 +0100
                                      Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-02-16 21:10 +0100
                                        Re: plans for eclipse luna in debian Thorsten Glaser <t.glaser@tarent.de> - 2016-02-17 13:10 +0100
                                Re: plans for eclipse luna in debian Christopher Hoskin <christopher.hoskin@gmail.com> - 2016-02-16 22:10 +0100
                                  Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-02-18 09:30 +0100
                                    Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-02-29 13:40 +0100
                                      Re: plans for eclipse luna in debian Markus Koschany <apo@debian.org> - 2016-02-29 13:40 +0100
                                        Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-03-10 15:00 +0100
                                          Re: plans for eclipse luna in debian Christopher Hoskin <christopher.hoskin@gmail.com> - 2016-03-11 00:20 +0100
                                            Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-03-11 09:40 +0100
                                              Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-03-11 10:30 +0100
                                                Re: plans for eclipse luna in debian Christopher Hoskin <christopher.hoskin@gmail.com> - 2016-03-11 11:30 +0100
                                  Re: plans for eclipse luna in debian Luca Vercelli <luca.vercelli.to@gmail.com> - 2016-02-21 18:40 +0100
                                    Re: plans for eclipse luna in debian Emmanuel Bourg <ebourg@apache.org> - 2016-02-29 14:10 +0100
                                    Re: plans for eclipse luna in debian Emmanuel Bourg <ebourg@apache.org> - 2016-02-29 14:10 +0100

Page 1 of 3  [1] 2 3  Next page →

#8447 — Re: plans for eclipse luna in debian

[Multipart message — attachments visible in raw view] — view raw

I agree with the question. Is there any plan to package a more recent
version of Eclipse, i.e. Eclipse 4.4 Luna or Eclipse 4.5 Mars?
3.8 is quite an old version, and I don't think it's a good practice to
use such an obsolete software. This is just my personal opinion, of course.
I would like to contribute to packaging, if needed.

Regards
Luca

> Hi,
> 
> I'm trying to package gnukhata (gitlab.com/gnukhata) and they use
> eclipse luna. When we run it with 3.8 version of ecipse-rcp, we get
> class not found exceptions. What are the plans for packaging luna?
>
> Thanks
> Praveen

[toc] | [next] | [standalone]

#8448

[Multipart message — attachments visible in raw view] — view raw

Am 09.10.2015 um 18:43 schrieb Luca Vercelli:
> I agree with the question. Is there any plan to package a more recent
> version of Eclipse, i.e. Eclipse 4.4 Luna or Eclipse 4.5 Mars?
> 3.8 is quite an old version, and I don't think it's a good practice to
> use such an obsolete software. This is just my personal opinion, of course.
> I would like to contribute to packaging, if needed.

Yes, we would like to see a newer version of Eclipse too. There is
always need for more packagers. The latest version of Eclipse requires a
lot of work before it can be included. In order to help us you could:

 - Find out where the latest sources of Eclipse 4.5 are located.
 - What build-dependencies are required? Do we have to package new ones
   for Debian? A work plan would be nice.
 - Create an initial Debian package of Eclipse similar to
   https://tracker.debian.org/pkg/eclipse


We probably have to start from scratch again (different build-system,
obsolete patches, new patches required, etc.).

As soon as the core package works again we have to find out if further
updates are necessary, so that the whole Eclipse ecosystem stays intact:

https://packages.debian.org/search?suite=all&section=all&arch=any&searchon=names&keywords=eclipse

Regards,

Markus

[toc] | [prev] | [next] | [standalone]

#8451

Thank you Markus.
It appears that there is not a single repo but a number of repos:
https://git.eclipse.org/c/?q=e4
and they use maven (v.3) to compile it.
I have a question: what is the feeling of this community for Maven? Can
it be used to compile Java programs during Debian packaging?

Regards,
Luca

Il 09/10/2015 19:19, Markus Koschany ha scritto:
> Am 09.10.2015 um 18:43 schrieb Luca Vercelli:
>> I agree with the question. Is there any plan to package a more recent
>> version of Eclipse, i.e. Eclipse 4.4 Luna or Eclipse 4.5 Mars?
>> 3.8 is quite an old version, and I don't think it's a good practice to
>> use such an obsolete software. This is just my personal opinion, of course.
>> I would like to contribute to packaging, if needed.
> Yes, we would like to see a newer version of Eclipse too. There is
> always need for more packagers. The latest version of Eclipse requires a
> lot of work before it can be included. In order to help us you could:
>
>  - Find out where the latest sources of Eclipse 4.5 are located.
>  - What build-dependencies are required? Do we have to package new ones
>    for Debian? A work plan would be nice.
>  - Create an initial Debian package of Eclipse similar to
>    https://tracker.debian.org/pkg/eclipse
>
>
> We probably have to start from scratch again (different build-system,
> obsolete patches, new patches required, etc.).
>
> As soon as the core package works again we have to find out if further
> updates are necessary, so that the whole Eclipse ecosystem stays intact:
>
> https://packages.debian.org/search?suite=all&section=all&arch=any&searchon=names&keywords=eclipse
>
> Regards,
>
> Markus
>

[toc] | [prev] | [next] | [standalone]

#8452

Le 10/10/2015 08:55, Luca Vercelli a écrit :

> I have a question: what is the feeling of this community for Maven? Can
> it be used to compile Java programs during Debian packaging?

Yes Maven is already used to build about 1/3 of the Java packages in
Debian. We run it in offline mode and redirect it to the system
repository (/usr/share/maven-repo) to get the artifacts.

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#8453

[Multipart message — attachments visible in raw view] — view raw

Am 10.10.2015 um 08:55 schrieb Luca Vercelli:
> Thank you Markus.
> It appears that there is not a single repo but a number of repos:
> https://git.eclipse.org/c/?q=e4
> and they use maven (v.3) to compile it.
> I have a question: what is the feeling of this community for Maven? Can
> it be used to compile Java programs during Debian packaging?

Hi Luca,

I think we can benefit from the good work of Eclipse's Fedora maintainer
and borrow some patches.

http://pkgs.fedoraproject.org/cgit/eclipse.git/

According to the spec file

http://pkgs.fedoraproject.org/cgit/eclipse.git/tree/eclipse.spec

they merge the sources from two git repositories into one tarball. I
believe we did something similar in the past. If we use the mh_make
script from maven-debian-helper, it should be possible to quickly create
an initial debian packaging structure.

Cheers,

Markus

[toc] | [prev] | [next] | [standalone]

#8461

A question about mh_make:
what about "Run tests while building the package?" and "Generate the
Javadoc while building the package?"? what should I answer?


Il 10/10/2015 11:35, Markus Koschany ha scritto:
> Am 10.10.2015 um 08:55 schrieb Luca Vercelli:
>> Thank you Markus.
>> It appears that there is not a single repo but a number of repos:
>> https://git.eclipse.org/c/?q=e4
>> and they use maven (v.3) to compile it.
>> I have a question: what is the feeling of this community for Maven? Can
>> it be used to compile Java programs during Debian packaging?
> Hi Luca,
>
> I think we can benefit from the good work of Eclipse's Fedora maintainer
> and borrow some patches.
>
> http://pkgs.fedoraproject.org/cgit/eclipse.git/
>
> According to the spec file
>
> http://pkgs.fedoraproject.org/cgit/eclipse.git/tree/eclipse.spec
>
> they merge the sources from two git repositories into one tarball. I
> believe we did something similar in the past. If we use the mh_make
> script from maven-debian-helper, it should be possible to quickly create
> an initial debian packaging structure.
>
> Cheers,
>
> Markus
>
>
>

[toc] | [prev] | [next] | [standalone]

#8462

Le 13/10/2015 09:44, Luca Vercelli a écrit :
> A question about mh_make:
> what about "Run tests while building the package?" and "Generate the
> Javadoc while building the package?"? what should I answer?

Hi Luca,

Start with the tests and the javadoc disabled, it will be easier. They
can be enabled later.

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#8479

[Multipart message — attachments visible in raw view] — view raw

Dear Marckus,
you were right. There is "a lot of work" in order to compile Eclipse Mars.
I attach a preliminary version of required dependencies. I am trying to
build Tycho before Eclipse, and I am still far away.

Luca

Il 09/10/2015 19:19, Markus Koschany ha scritto:
> The latest version of Eclipse requires a
> lot of work before it can be included

[toc] | [prev] | [next] | [standalone]

#8481

[Multipart message — attachments visible in raw view] — view raw

Am 17.10.2015 um 15:02 schrieb Luca Vercelli:
> Dear Marckus,
> you were right. There is "a lot of work" in order to compile Eclipse Mars.
> I attach a preliminary version of required dependencies. I am trying to
> build Tycho before Eclipse, and I am still far away.
> 

Hi Luca,

it always seems overwhelming at first, especially because Eclipse is one
of the most complex packages you will ever see, but you have already
taken an important step forward by compiling those dependency lists. The
next step is to split the work into smaller parts and to package
required dependencies.

Dependencies with different versions can be a problem but they don't
have to be. We use maven.rules to rewrite dependency versions, so
version 1.2.3 becomes 1.x or debian. Then again sometimes we have to
package a newer upstream release to satisfy the build-dependency.


Dependencies we don't have:

We have jetty and osgi-annotation. The atinject and glassfish
dependencies should be there too. Eclipse-license can probably be
ignored. We have to write our own debian/copyright file anyway.

In general it looks like we already ship most of the required
dependencies. It would be a big help, if you want to work on Tycho. I
will try to create an initial debian directory for Eclipse. If you
struggle with a dependency, just ignore it for now and add it to
maven.ignoreRules. After that the work flow looks like that:

1. Try to build the package (debuild -us -uc)
2. Package fails with error message: artifact xyz missing
3. Artifact already packaged for Debian?
   yes -> Add build-dependency to debian/control and add a new rule to
   maven.rules (not always required)

   no -> package dependency, remove it from maven.ignoreRules, add it
   to debian/control, write a new rule for maven.rules

4. Repeat step 1-3 until the package can be built from source.

The build can fail because of incompatible versions too. In this case we
should take a closer look and decide whether we have to package a newer
version or if we can write a patch to circumvent the issue. Whatever is
simpler for now. Thumb of rule is: Get a working package with the
minimum number of build-dependencies and optimize everything after the
whole thing compiles.

Cheers,

Markus

[toc] | [prev] | [next] | [standalone]

#8484

[Multipart message — attachments visible in raw view] — view raw

Hi,

I have committed the initial and incomplete Debian directory for Eclipse
4.5.1.

https://anonscm.debian.org/cgit/pkg-java/eclipse.git/tree/?h=experimental

I have explained in README.source how one can obtain the original
sources. I have also discovered that we need JDK 8 and Maven 3 for
building this release. mh_make didn't complete because Tycho hasn't been
packaged yet and I think this should be the first step to bring a newer
version of Eclipse to Debian.

Fun fact: Eclipse 4.5.1 contains 553 different pom.xml files. :E

Markus

[toc] | [prev] | [next] | [standalone]

#8495

I am not an expert with mh_make, however I see a problem here.
Eclipse build depends on Tycho, however Tycho build depends on both
Eclipse and Tycho itself!
So, two problems:
(1) mh_make fails for both projects.
Markus, can you explain me how were you able to build the base structure
of Eclipse without mh_make? I should do the same with Tycho.
(2) How to build everything?
Fedora packagers were able to build just a tiny part of Tycho (a
"bootstrap"), then a tiny part of Eclipse, then Tycho, and at last
Eclipse. What about Debian?

Thank you!


Il 18/10/2015 17:49, Markus Koschany ha scritto:
> Hi,
>
> I have committed the initial and incomplete Debian directory for Eclipse
> 4.5.1.
>
> https://anonscm.debian.org/cgit/pkg-java/eclipse.git/tree/?h=experimental
>
> I have explained in README.source how one can obtain the original
> sources. I have also discovered that we need JDK 8 and Maven 3 for
> building this release. mh_make didn't complete because Tycho hasn't been
> packaged yet and I think this should be the first step to bring a newer
> version of Eclipse to Debian.
>
> Fun fact: Eclipse 4.5.1 contains 553 different pom.xml files. :E
>
> Markus
>

[toc] | [prev] | [next] | [standalone]

#8498

[Multipart message — attachments visible in raw view] — view raw

Am 20.10.2015 um 12:58 schrieb Luca Vercelli:
> I am not an expert with mh_make, however I see a problem here.
> Eclipse build depends on Tycho, however Tycho build depends on both
> Eclipse and Tycho itself!

Indeed that is nasty. But it looks like the Fedora maintainers have
solved this issue too. [1] We need to do something similar for Debian to
break this circular dependency.

> So, two problems:
> (1) mh_make fails for both projects.
> Markus, can you explain me how were you able to build the base structure
> of Eclipse without mh_make? I should do the same with Tycho.

mh_make often chokes on bigger projects with a lot of unpackaged
dependencies. I simply ignored as many dependencies as I could and you
can find the end result in maven.rules and maven.ignoreRules. Then I
used the current packaging for Eclipse as a template. It should be
sufficient to start with a minimal debian/rules files. In the first
phase we only have to modify the maven.* files and debian/control. For
Tycho you can basically do the same.

If you can answer the question why mh_make fails with Tycho, you will
know what dependency we should package first. Just let me know what
dependencies we need for Tycho and I can lend you a hand.


> (2) How to build everything?
> Fedora packagers were able to build just a tiny part of Tycho (a
> "bootstrap"), then a tiny part of Eclipse, then Tycho, and at last
> Eclipse. What about Debian?

AFAIK they provide different build options. The bootstrap is one of them
but otherwise Eclipse and Tycho build-depend on each other. I don't know
how to solve this properly yet but I expect we will end up with doing
something similar. Remember that the optimization step is always the
last part, so feel free to solve this issue with the least amount of effort.

Markus


[1] http://pkgs.fedoraproject.org/cgit/tycho.git/tree/

[toc] | [prev] | [next] | [standalone]

#8499

Hi,

I'm from the Eclipse community. I've been involved with Eclipse for over 
10y where I've contributed to the previous build mechanism and to the 
Tycho based one. If you need, I can help shed some light on the why of 
things so you can save time navigating this by yourself.
That said, I'm not familiar with the way fedora have done things (but I 
know one of the maintainer of the Eclipse build there if we need more 
details), though I assume they probably have to first white list a 
number of bundles to bootstrap tycho, then build the pieces originally 
white listed, and finally rebuild tycho and continue on.

HTH

Pascal

On 15-10-20 01:06 PM, Markus Koschany wrote:
> Am 20.10.2015 um 12:58 schrieb Luca Vercelli:
>> I am not an expert with mh_make, however I see a problem here.
>> Eclipse build depends on Tycho, however Tycho build depends on both
>> Eclipse and Tycho itself!
> Indeed that is nasty. But it looks like the Fedora maintainers have
> solved this issue too. [1] We need to do something similar for Debian to
> break this circular dependency.
>
>> So, two problems:
>> (1) mh_make fails for both projects.
>> Markus, can you explain me how were you able to build the base structure
>> of Eclipse without mh_make? I should do the same with Tycho.
> mh_make often chokes on bigger projects with a lot of unpackaged
> dependencies. I simply ignored as many dependencies as I could and you
> can find the end result in maven.rules and maven.ignoreRules. Then I
> used the current packaging for Eclipse as a template. It should be
> sufficient to start with a minimal debian/rules files. In the first
> phase we only have to modify the maven.* files and debian/control. For
> Tycho you can basically do the same.
>
> If you can answer the question why mh_make fails with Tycho, you will
> know what dependency we should package first. Just let me know what
> dependencies we need for Tycho and I can lend you a hand.
>
>
>> (2) How to build everything?
>> Fedora packagers were able to build just a tiny part of Tycho (a
>> "bootstrap"), then a tiny part of Eclipse, then Tycho, and at last
>> Eclipse. What about Debian?
> AFAIK they provide different build options. The bootstrap is one of them
> but otherwise Eclipse and Tycho build-depend on each other. I don't know
> how to solve this properly yet but I expect we will end up with doing
> something similar. Remember that the optimization step is always the
> last part, so feel free to solve this issue with the least amount of effort.
>
> Markus
>
>
> [1] http://pkgs.fedoraproject.org/cgit/tycho.git/tree/
>

[toc] | [prev] | [next] | [standalone]

#8512

Dear Pascal,
I have a question. I'm trying to build Tycho, and all pom's  refer to
the "packaging eclipse-plugin". What is this? Offline Maven gives error
"Unknown packaging: eclipse-plugin". I suppose its source code is
somewhere else outside Tycho.


Il 21/10/2015 03:46, Pascal Rapicault ha scritto:
> Hi,
>
> I'm from the Eclipse community. I've been involved with Eclipse for
> over 10y where I've contributed to the previous build mechanism and to
> the Tycho based one. If you need, I can help shed some light on the
> why of things so you can save time navigating this by yourself.
> That said, I'm not familiar with the way fedora have done things (but
> I know one of the maintainer of the Eclipse build there if we need
> more details), though I assume they probably have to first white list
> a number of bundles to bootstrap tycho, then build the pieces
> originally white listed, and finally rebuild tycho and continue on.
>
> HTH
>
> Pascal
>
> On 15-10-20 01:06 PM, Markus Koschany wrote:
>> Am 20.10.2015 um 12:58 schrieb Luca Vercelli:
>>> I am not an expert with mh_make, however I see a problem here.
>>> Eclipse build depends on Tycho, however Tycho build depends on both
>>> Eclipse and Tycho itself!
>> Indeed that is nasty. But it looks like the Fedora maintainers have
>> solved this issue too. [1] We need to do something similar for Debian to
>> break this circular dependency.
>>
>>> So, two problems:
>>> (1) mh_make fails for both projects.
>>> Markus, can you explain me how were you able to build the base
>>> structure
>>> of Eclipse without mh_make? I should do the same with Tycho.
>> mh_make often chokes on bigger projects with a lot of unpackaged
>> dependencies. I simply ignored as many dependencies as I could and you
>> can find the end result in maven.rules and maven.ignoreRules. Then I
>> used the current packaging for Eclipse as a template. It should be
>> sufficient to start with a minimal debian/rules files. In the first
>> phase we only have to modify the maven.* files and debian/control. For
>> Tycho you can basically do the same.
>>
>> If you can answer the question why mh_make fails with Tycho, you will
>> know what dependency we should package first. Just let me know what
>> dependencies we need for Tycho and I can lend you a hand.
>>
>>
>>> (2) How to build everything?
>>> Fedora packagers were able to build just a tiny part of Tycho (a
>>> "bootstrap"), then a tiny part of Eclipse, then Tycho, and at last
>>> Eclipse. What about Debian?
>> AFAIK they provide different build options. The bootstrap is one of them
>> but otherwise Eclipse and Tycho build-depend on each other. I don't know
>> how to solve this properly yet but I expect we will end up with doing
>> something similar. Remember that the optimization step is always the
>> last part, so feel free to solve this issue with the least amount of
>> effort.
>>
>> Markus
>>
>>
>> [1] http://pkgs.fedoraproject.org/cgit/tycho.git/tree/
>>
>

[toc] | [prev] | [next] | [standalone]

#8514

Hi Luca,

Tycho is defining the eclipse-plugin packaging type 
(https://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-maven-plugin/src/main/resources/META-INF/plexus/components.xml) 


Pascal

On 25/10/2015 5:12 PM, Luca Vercelli wrote:
> Dear Pascal,
> I have a question. I'm trying to build Tycho, and all pom's  refer to
> the "packaging eclipse-plugin". What is this? Offline Maven gives error
> "Unknown packaging: eclipse-plugin". I suppose its source code is
> somewhere else outside Tycho.
>
>
> Il 21/10/2015 03:46, Pascal Rapicault ha scritto:
>> Hi,
>>
>> I'm from the Eclipse community. I've been involved with Eclipse for
>> over 10y where I've contributed to the previous build mechanism and to
>> the Tycho based one. If you need, I can help shed some light on the
>> why of things so you can save time navigating this by yourself.
>> That said, I'm not familiar with the way fedora have done things (but
>> I know one of the maintainer of the Eclipse build there if we need
>> more details), though I assume they probably have to first white list
>> a number of bundles to bootstrap tycho, then build the pieces
>> originally white listed, and finally rebuild tycho and continue on.
>>
>> HTH
>>
>> Pascal
>>
>> On 15-10-20 01:06 PM, Markus Koschany wrote:
>>> Am 20.10.2015 um 12:58 schrieb Luca Vercelli:
>>>> I am not an expert with mh_make, however I see a problem here.
>>>> Eclipse build depends on Tycho, however Tycho build depends on both
>>>> Eclipse and Tycho itself!
>>> Indeed that is nasty. But it looks like the Fedora maintainers have
>>> solved this issue too. [1] We need to do something similar for Debian to
>>> break this circular dependency.
>>>
>>>> So, two problems:
>>>> (1) mh_make fails for both projects.
>>>> Markus, can you explain me how were you able to build the base
>>>> structure
>>>> of Eclipse without mh_make? I should do the same with Tycho.
>>> mh_make often chokes on bigger projects with a lot of unpackaged
>>> dependencies. I simply ignored as many dependencies as I could and you
>>> can find the end result in maven.rules and maven.ignoreRules. Then I
>>> used the current packaging for Eclipse as a template. It should be
>>> sufficient to start with a minimal debian/rules files. In the first
>>> phase we only have to modify the maven.* files and debian/control. For
>>> Tycho you can basically do the same.
>>>
>>> If you can answer the question why mh_make fails with Tycho, you will
>>> know what dependency we should package first. Just let me know what
>>> dependencies we need for Tycho and I can lend you a hand.
>>>
>>>
>>>> (2) How to build everything?
>>>> Fedora packagers were able to build just a tiny part of Tycho (a
>>>> "bootstrap"), then a tiny part of Eclipse, then Tycho, and at last
>>>> Eclipse. What about Debian?
>>> AFAIK they provide different build options. The bootstrap is one of them
>>> but otherwise Eclipse and Tycho build-depend on each other. I don't know
>>> how to solve this properly yet but I expect we will end up with doing
>>> something similar. Remember that the optimization step is always the
>>> last part, so feel free to solve this issue with the least amount of
>>> effort.
>>>
>>> Markus
>>>
>>>
>>> [1] http://pkgs.fedoraproject.org/cgit/tycho.git/tree/
>>>

[toc] | [prev] | [next] | [standalone]

#8505

[Multipart message — attachments visible in raw view] — view raw

I suppose the initial Tycho repository should be something like the
attached one.
I downloaded upstream source from
http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/snapshot/org.eclipse.tycho-tycho-0.23.0.tar.xz


Il 20/10/2015 19:06, Markus Koschany ha scritto:
> Am 20.10.2015 um 12:58 schrieb Luca Vercelli:
>> I am not an expert with mh_make, however I see a problem here.
>> Eclipse build depends on Tycho, however Tycho build depends on both
>> Eclipse and Tycho itself!
> Indeed that is nasty. But it looks like the Fedora maintainers have
> solved this issue too. [1] We need to do something similar for Debian to
> break this circular dependency.
>
>> So, two problems:
>> (1) mh_make fails for both projects.
>> Markus, can you explain me how were you able to build the base structure
>> of Eclipse without mh_make? I should do the same with Tycho.
> mh_make often chokes on bigger projects with a lot of unpackaged
> dependencies. I simply ignored as many dependencies as I could and you
> can find the end result in maven.rules and maven.ignoreRules. Then I
> used the current packaging for Eclipse as a template. It should be
> sufficient to start with a minimal debian/rules files. In the first
> phase we only have to modify the maven.* files and debian/control. For
> Tycho you can basically do the same.
>
> If you can answer the question why mh_make fails with Tycho, you will
> know what dependency we should package first. Just let me know what
> dependencies we need for Tycho and I can lend you a hand.
>
>
>> (2) How to build everything?
>> Fedora packagers were able to build just a tiny part of Tycho (a
>> "bootstrap"), then a tiny part of Eclipse, then Tycho, and at last
>> Eclipse. What about Debian?
> AFAIK they provide different build options. The bootstrap is one of them
> but otherwise Eclipse and Tycho build-depend on each other. I don't know
> how to solve this properly yet but I expect we will end up with doing
> something similar. Remember that the optimization step is always the
> last part, so feel free to solve this issue with the least amount of effort.
>
> Markus
>
>
> [1] http://pkgs.fedoraproject.org/cgit/tycho.git/tree/
>

[toc] | [prev] | [next] | [standalone]

#8522

I found out that eclipse depends on sat4j 2.3.4, and we have 2.3.3.
There are some classes more in 2.3.4, so it is required.
I have built 2.3.4 from source, it's quite easy. I just had to write
some pom's myself. how can I share these?
Thank you.


Il 20/10/2015 19:06, Markus Koschany ha scritto:
> Am 20.10.2015 um 12:58 schrieb Luca Vercelli:
>> I am not an expert with mh_make, however I see a problem here.
>> Eclipse build depends on Tycho, however Tycho build depends on both
>> Eclipse and Tycho itself!
> Indeed that is nasty. But it looks like the Fedora maintainers have
> solved this issue too. [1] We need to do something similar for Debian to
> break this circular dependency.
>
>> So, two problems:
>> (1) mh_make fails for both projects.
>> Markus, can you explain me how were you able to build the base structure
>> of Eclipse without mh_make? I should do the same with Tycho.
> mh_make often chokes on bigger projects with a lot of unpackaged
> dependencies. I simply ignored as many dependencies as I could and you
> can find the end result in maven.rules and maven.ignoreRules. Then I
> used the current packaging for Eclipse as a template. It should be
> sufficient to start with a minimal debian/rules files. In the first
> phase we only have to modify the maven.* files and debian/control. For
> Tycho you can basically do the same.
>
> If you can answer the question why mh_make fails with Tycho, you will
> know what dependency we should package first. Just let me know what
> dependencies we need for Tycho and I can lend you a hand.
>
>
>> (2) How to build everything?
>> Fedora packagers were able to build just a tiny part of Tycho (a
>> "bootstrap"), then a tiny part of Eclipse, then Tycho, and at last
>> Eclipse. What about Debian?
> AFAIK they provide different build options. The bootstrap is one of them
> but otherwise Eclipse and Tycho build-depend on each other. I don't know
> how to solve this properly yet but I expect we will end up with doing
> something similar. Remember that the optimization step is always the
> last part, so feel free to solve this issue with the least amount of effort.
>
> Markus
>
>
> [1] http://pkgs.fedoraproject.org/cgit/tycho.git/tree/
>

[toc] | [prev] | [next] | [standalone]

#8523

Il 31/10/2015 15:33, Michael Tautschnig ha scritto:
> Hi,
>
> On Sat, Oct 31, 2015 at 13:23:41 +0100, Luca Vercelli wrote:
>> I found out that eclipse depends on sat4j 2.3.4, and we have 2.3.3.
>> There are some classes more in 2.3.4, so it is required.
>> I have built 2.3.4 from source, it's quite easy. I just had to write
>> some pom's myself. how can I share these?
> [...]
>
> It may have been worth getting in touch :-)
You're right, sorry!
> - as sat4j maintainer in Debian I
> should apologise that I had failed to notice that 2.3.4 (and even 2.3.5) are
> out. The SVN tag names have changed, hence I hadn't been notified in any way.
>
> Now I am wondering whether it would be ok to package 2.3.5 straight away, or
> does Eclipse strictly depend on 2.3.4?

Well, I'm not sure of this, but I think 2.3.5 will be fine.
Also, w.r.t. the old package sat4j, it didn't put any link in
/usr/share/maven-repo. (I just created these links for myself using mvn
install).

Thank you
Luca

> Also: I'd be more than happy to have share sat4j maintenance.
>
> Best,
> Michael
>

[toc] | [prev] | [next] | [standalone]

#8525

[Multipart message — attachments visible in raw view] — view raw

Am 31.10.2015 um 15:46 schrieb Luca Vercelli:
[...]
>> Now I am wondering whether it would be ok to package 2.3.5 straight away, or
>> does Eclipse strictly depend on 2.3.4?
> 
> Well, I'm not sure of this, but I think 2.3.5 will be fine.
> Also, w.r.t. the old package sat4j, it didn't put any link in
> /usr/share/maven-repo. (I just created these links for myself using mvn
> install).
> 
> Thank you
> Luca

I would go for the latest release. I agree that adding maven artifacts
to sat4j is useful. Please upload new revisions of packages to

http://mentors.debian.net/.
http://mentors.debian.net/intro-maintainers

and ask for a review on this list. Is sat4j 2.3.5 also compatible with
the current version of Eclipse? Then we can upload the package straight
to unstable, otherwise I suggest to use the experimental distribution
for now.

>> Also: I'd be more than happy to have share sat4j maintenance.
>>
>> Best,
>> Michael

Why not maintain sat4j as part of the Java team? It's no guarantee that
the maintenance effort will automatically drop to zero but some bugs can
be fixed more efficiently.

Cheers,

Markus

[toc] | [prev] | [next] | [standalone]

#8532

Sat4j 2.3.5 is already used by Eclipse.
The 2.3.6 release should be released before the end of November.

On 15-10-31 11:34 AM, Markus Koschany wrote:
> Am 31.10.2015 um 15:46 schrieb Luca Vercelli:
> [...]
>>> Now I am wondering whether it would be ok to package 2.3.5 straight away, or
>>> does Eclipse strictly depend on 2.3.4?
>> Well, I'm not sure of this, but I think 2.3.5 will be fine.
>> Also, w.r.t. the old package sat4j, it didn't put any link in
>> /usr/share/maven-repo. (I just created these links for myself using mvn
>> install).
>>
>> Thank you
>> Luca
> I would go for the latest release. I agree that adding maven artifacts
> to sat4j is useful. Please upload new revisions of packages to
>
> http://mentors.debian.net/.
> http://mentors.debian.net/intro-maintainers
>
> and ask for a review on this list. Is sat4j 2.3.5 also compatible with
> the current version of Eclipse? Then we can upload the package straight
> to unstable, otherwise I suggest to use the experimental distribution
> for now.
>
>>> Also: I'd be more than happy to have share sat4j maintenance.
>>>
>>> Best,
>>> Michael
> Why not maintain sat4j as part of the Java team? It's no guarantee that
> the maintenance effort will automatically drop to zero but some bugs can
> be fixed more efficiently.
>
> Cheers,
>
> Markus
>

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.maint.java

csiph-web