> Le 29/05/2013 17:06, Manfred Moser a écrit :
>
>> What are you deploying to if you are not using a repo manager?
>
> I simply deploy to a remote server via SSH. The artifacts are served by
> Apache.
Ah... ouch.
>> And why not use e.g. Nexus and just have the snapshot cleanup task
>> running?
>
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).
My pr
Hi all,
I resurrected the tagsoup package which was removed from testing 3
months ago. This package is required for packaging Apache Tika.
Here is the changelog:
* Adopting package
* New upstream release
- Added a patch to fix the version number
* The Maven artifacts are now deployed t
Le 29/05/2013 17:06, Manfred Moser a écrit :
> What are you deploying to if you are not using a repo manager?
I simply deploy to a remote server via SSH. The artifacts are served by
Apache.
> And why not use e.g. Nexus and just have the snapshot cleanup task running?
Because so far I didn't ne
> 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? S
> 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
> 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 Mav
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 3. But
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? Should we split
Hi all,
I updated the guava-libraries package to the latest upstream release.
The only significant change is the addition of a new dependency on
libatinject-jsr330-api-java.
http://mentors.debian.net/package/guava-libraries
Thank you for your reviews,
Emmanuel Bourg
signature.asc
Description
11 matches
Mail list logo