On Mon, Mar 9, 2015 at 7:05 AM, Miguel Landaeta wrote:
>> Ideally we should switch maven-debian-helper to Maven 3 as soon as
>> possible after the end of the freeze, this will leaves us a full
>> development cycle to complete the transition to Maven 3. I don't
>>
; > this. It is normal with maven2 but since I didn't see any patch for
> > maven, I just wanted to check with team.
>
> Yes this is normal, the super pom has to be modified everytime a core
> plugin is updated. And as we update the plugins for Maven 3 we'll have
> to f
ted to check with team.
Yes this is normal, the super pom has to be modified everytime a core
plugin is updated. And as we update the plugins for Maven 3 we'll have
to fork them and maintain an old version for Maven 2 and a new one for
Maven 3, just like you did with the compiler plugin.
Hi,
I'm packaging jruby 1.7.x (and 9.0.0.0) and it build depends on
maven-compiler-plugin (>= 3.0), so I need to use Maven 3.
When I try to build jruby using Maven 3, it usually fails due to some
missing plugins releases in Debian, e.g.:
maven-antrun-plugin:1.3
maven-dependency-pl
I would suggest to do that..
>> And apart from storage consumption.. is there any other problem?
>
> The last time I tried Maven 3 I didn't like the output, it looked less
> readable to me. I just have to get used to it I guess.
Considering that Maven 2 is not developed anymor
Hi,
On 29.5.2013 16:22, Manfred Moser wrote:
Imho we should sort out all situations where people think they have to
stick to Maven 2, migrate them and then deprecate support for Maven 2.
FYI I've started to implement Maven 3 support into maven-debian-helper
(dh build only, no cdbs yet)
didn't need it. And I'd rather not have a daemon
running continuously and eating resources on my server just for cleaning
a few artifacts once a week.
> And apart from storage consumption.. is there any other problem?
The last time I tried Maven 3 I didn't like the output, it lo
> Hi all,
>
> There is an increasing number of Maven plugins that require Maven 3 and
> can't be upgraded without breaking Maven 2. For example
> maven-install-plugin 2.3 works with Maven 2 and Maven 3, but the version
> 2.4 is for Maven 3 only.
>
> What's the p
> Le 29/05/2013 16:46, Manfred Moser a écrit :
>
>> Can you clarify the details of what you mean with that?
>
> See:
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments
>
> I can no longer deploy non timestamped snapshots to my
Le 29/05/2013 16:46, Manfred Moser a écrit :
> Can you clarify the details of what you mean with that?
See:
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments
I can no longer deploy non timestamped snapshots to my private
repo
> that was removed from Maven 3.
Can you clarify the details of what you mean with that?
manfred
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/f
Le 29/05/2013 16:22, Manfred Moser a écrit :
> Imho we should sort out all situations where people think they have to
> stick to Maven 2, migrate them and then deprecate support for Maven 2.
I personally stick to Maven 2 because I need the uniqueVersion feature
that was removed from Maven
Hi all,
There is an increasing number of Maven plugins that require Maven 3 and
can't be upgraded without breaking Maven 2. For example
maven-install-plugin 2.3 works with Maven 2 and Maven 3, but the version
2.4 is for Maven 3 only.
What's the proper way to handle this situation?
Ioan,
On 04/01/2012 09:01, Ioan Eugen Stan wrote:
2011/12/30 Damien Raude-Morvan:
Hi Java team!
Maven 3.x is now available in experimental in a new _maven_ debian package.
You'll also need updated _maven2_ package (>= 2.2.1-11) to allow side-by-side
installation (I'm using al
2011/12/30 Damien Raude-Morvan :
> Hi Java team!
>
> Maven 3.x is now available in experimental in a new _maven_ debian package.
> You'll also need updated _maven2_ package (>= 2.2.1-11) to allow side-by-side
> installation (I'm using alternatives to allow user to cho
On 11-12-30 07:45 AM, Damien Raude-Morvan wrote:
Hi Java team!
Maven 3.x is now available in experimental in a new _maven_ debian package.
You'll also need updated _maven2_ package (>= 2.2.1-11) to allow side-by-side
installation (I'm using alternatives to allow user to choose betw
Hi Java team!
Maven 3.x is now available in experimental in a new _maven_ debian package.
You'll also need updated _maven2_ package (>= 2.2.1-11) to allow side-by-side
installation (I'm using alternatives to allow user to choose between "mvn" cli
tool).
Please test an
Le mercredi 21 décembre 2011 11:28:07, Ioan Eugen Stan a écrit :
> Hello everybody,
Hi Ioan!
> I wish to see maven 3 in the next Debian release so I decided to give a
> hand in packaging it. I have some experience in using maven but I'm not
> very familiar with it's inter
Hello everybody,
I wish to see maven 3 in the next Debian release so I decided to give a
hand in packaging it. I have some experience in using maven but I'm not
very familiar with it's internals. Kind of the same goes for I'm sure
this will change once I start diving in.
I
Le mardi 15 novembre 2011 23:46:21, Ludovic Claude a écrit :
> Hello Damien,
Hi Ludovic!
> There is some progress on my side.
> Could you sponsor the following packages:
>
> maven-ant-helper, maven-repo-helper, apache-pom, commons-parent,
> commons-lang
Great! I'll have a look during this week.
st updated Maven3 wiki page [1] with my latest ITPs. I've also tried to
cleanup each dependencies level. From a quick overview, it seems that we'll
need to keep some duplicate packages to have both Maven 2.x and Maven 3.x
dependencies at the same time in archive...
Right now, I'
Hi Team!
I've just updated Maven3 wiki page [1] with my latest ITPs. I've also tried to
cleanup each dependencies level. From a quick overview, it seems that we'll
need to keep some duplicate packages to have both Maven 2.x and Maven 3.x
dependencies at the same time in archiv
Hi Damien,
On Tue, Aug 30, 2011 at 9:11 PM, Damien Raude-Morvan
wrote:
> - packages some missing "parent" poms (into multi or single source tarball)
I can start working on that next week. I would prefer a single source
and binary package ('maven-parent-poms') for all pom files. We can
split it l
Le mardi 30 août 2011 09:59:41, Torsten Werner a écrit :
> Hi Ludovic, Damien & others,
>
> I've looked at <http://wiki.debian.org/Java/Maven3>. Is that page more
> or less up to date? What would be a good task to start with if someone
> want to contribute to packagi
Hi Ludovic, Damien & others,
I've looked at <http://wiki.debian.org/Java/Maven3>. Is that page more
or less up to date? What would be a good task to start with if someone
want to contribute to packaging Maven 3?
Cheers,
Torsten
--
To UNSUBSCRIBE, email to debian-java-requ...@l
25 matches
Mail list logo
