Yes, definitely. The 1.0 release was a necessary prerequisite for
testing, but now that there is a descriptor out there that people could
file issues against, we can start asking around to see whether other
projects can give it a try.
Incidentally, where would we file issues for this descriptor? Thoughts?
-john
Arnaud HERITIER wrote:
Before moving it to apache pom, we could ask to some others projects to
validate it ?
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Sun, Aug 23, 2009 at 10:17 PM, Brian Fox <bri...@infinity.nu> wrote:
We still have some fixes to make before we promote it apache wide.
Once it's working for all our stuff we can upgrade the apache pom.
On Fri, Aug 21, 2009 at 7:08 PM, Arnaud HERITIER<aherit...@gmail.com>
wrote:
perhaps you could forward this to all PMCs ?
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Sat, Aug 22, 2009 at 1:00 AM, John Casey <jdca...@apache.org> wrote:
It appears that the site/repository synchronization is moving slowly, so
please be patient and these artifacts and site updates should be showing
up
before long. I want to make sure I get this announcement out before I
forget
it, though.
---
The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.
This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build output) that
are the subject of an ASF release vote.
http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/
This assembly descriptor should be coming to a parent POM near you, and
should eventually be an automatic part of every ASF release. For now, it
has been configured into the release process for Maven projects that
inherit from maven-parent version 13 (also recently released). If you
want to try out the source-release descriptor in the meantime, you can
include a configuration like the following:
<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-4</version>
<dependencies>
<dependency>
<groupId>org.apache.apache.resources</groupId>
<artifactId>apache-source-release-assembly-descriptor</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
<executions>
<execution>
<id>source-release</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptorRefs>
<descriptorRef>source-release</descriptorRef>
</descriptorRefs>
<tarLongFileMode>gnu</tarLongFileMode>
<runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Enjoy,
The Maven Team
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
