>
> Such a project would be built after its child modules. Basically, the
> occurrence of in a POM should no longer establish any kind of
> dependency between the parent project and the inheriting project, only
> aggregation would do so.
So in essence we are relying on the resolution of this arti
Vote open for 72 hours.
Ping
Ping
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
kohsuke has started the process to push animal sniffer to central
Sent from my [rhymes with myPod] ;-)
On 14 Aug 2009, at 21:47, Arnaud HERITIER wrote:
yes but 2.1 generates wrong pgp.I though we could use animal-sniffer
to be
able to use java > 1.4 to do our releases without risk but I sa
+1 (non-apache committer) I want to release versions-maven-plugin
Stephen
2009/8/14 Arnaud HERITIER :
> Hi,
>
> We solved 4
> issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14868
>
> There are no issue left in JIRA. We need this release for the nex
Hi,
We solved 4
issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14868
There are no issue left in JIRA. We need this release for the next
version of the versions-maven-plugin @ mojo.
Staging
repo:https://repository.apache.org/content/repositories/m
yes but 2.1 generates wrong pgp.I though we could use animal-sniffer to be
able to use java > 1.4 to do our releases without risk but I saw a thread
this morning saying that it wasn't yet available in central :-(
I did my release with 2.0.10 but I had to decrypt my passwords :-(
On Fri, Aug 14,
You only have permissions to deploy artifacts based on the groupId for
configured projects. IOW you as a Maven committer can deploy
/org/apache/maven/.* but commons-monitoring is not configured in
repository.apache.org so you have no permissions for those artifacts.
You can get it migrated here:
ht
Arnaud HERITIER wrote:
> Thx to Stephane Nicoll who pointed me on the problem.The last bullet in
> prerequisites says that we can use maven 2.2, but it is false because we
> cannot use it to release plugins or shared components. I didn't understand
> that it was maven which didn't want to start.
>
Thx to Stephane Nicoll who pointed me on the problem.The last bullet in
prerequisites says that we can use maven 2.2, but it is false because we
cannot use it to release plugins or shared components. I didn't understand
that it was maven which didn't want to start.
I have to come back to maven 2.0.
Hi,
I'm releasing a shared component (maven-common-artifact-filter) and I'm
following our guide (
http://maven.apache.org/developers/release/releasing.html) which says to use
java 1.4.
When I launch the release:prepare goal I receive the error :
Java specification version: 1.4
This release of M
Brian Fox wrote:
Project Ordering
A project with packaging pom can serve both as a parent POM and as an
aggregator POM. [...] For this reason, the project sorter needs to
be changed to mark an aggregator POM as a dependant of all its
modules.
What happens in the normal case where the pom is b
11 matches
Mail list logo
