Closed GoogleCodeExporter closed 9 years ago
Original comment by allain.lalonde
on 30 Oct 2009 at 6:38
$ svn commit -m "Issue 146 ; adding explicit plugin versions, cleaning up maven
3.0-alpha warnings" .
Sending core/pom.xml
Sending examples/pom.xml
Sending extras/pom.xml
Sending parent/pom.xml
Sending swt/pom.xml
Sending swt-examples/pom.xml
Transmitting file data ......
Committed revision 893.
Original comment by heue...@gmail.com
on 27 Nov 2009 at 7:27
It appears that the pre-defined assembly descriptors will not be sufficient for
our
needs. E.g., the parent module must be excluded for the bin descriptor to work
$ mvn -DdescriptorId=bin assembly:assembly
...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4:assembly
(default-cli) on
project piccolo2d-parent:
Failed to create assembly: Error creating assembly archive bin: You must set at
least one file.
and license-piccolo.txt and ReleaseNotes.txt are not included by default
http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#bin
<fileSets>
<fileSet>
<includes>
<include>${project.basedir}/README*</include>
<include>${project.basedir}/LICENSE*</include>
<include>${project.basedir}/NOTICE*</include>
</includes>
Custom assembly descriptors will need to be created.
Original comment by heue...@gmail.com
on 3 Dec 2009 at 4:01
Still working on this. Maven assembly plugin is driving me nuts.
I'd like the output to match what the attached shell scripts do.
Original comment by heue...@gmail.com
on 12 Dec 2009 at 1:12
Attachments:
I'm tentatively planning to cut a 1.3-beta release on Friday 18 Dec via the
attached
shell scripts, or via the maven assembly plugin if I can get that working by
then.
Please let me know if the artifacts created by the scripts above don't look
right.
Original comment by heue...@gmail.com
on 15 Dec 2009 at 8:42
Attaching new versions of the build scripts, as used to cut the 1.3-rc1
release.
Should these be committed to svn?
Original comment by heue...@gmail.com
on 19 Jan 2010 at 4:16
Attachments:
I'd say so, why not? put them in a scripts directory.
Original comment by allain.lalonde
on 19 Jan 2010 at 4:26
Keeping this issue open until after 1.3 is released, in case any changes need
to be
made to the poms to support uploading to maven central.
Original comment by heue...@gmail.com
on 3 Mar 2010 at 3:15
Patch to tags/release-1.3 to support signing and deploying to Sonatype OSS Nexus
instance for sync to maven central repository. Will commit to
branches/release-1.3
and trunk after this process runs its course.
Original comment by heue...@gmail.com
on 23 Mar 2010 at 4:51
Attachments:
Updated patch attached.
Original comment by heue...@gmail.com
on 31 Mar 2010 at 1:53
Attachments:
$ svn commit -m "Issue 146 ; committing patch to trunk" parent/pom.xml
Sending parent/pom.xml
Transmitting file data .
Committed revision 1001.
$ svn commit -m "Issue 146 ; committing patch to release 1.3 branch"
parent/pom.xml
Sending parent/pom.xml
Transmitting file data .
Committed revision 1002.
Original comment by heue...@gmail.com
on 31 Mar 2010 at 2:17
[deleted comment]
Original comment by heue...@gmail.com
on 26 Nov 2013 at 8:47
Original issue reported on code.google.com by
heue...@gmail.com
on 30 Oct 2009 at 6:02