search

kahntang / as3corelib

Automatically exported from code.google.com/p/as3corelib
0 stars 0 forks source link

Need maven artifacts for this library #73

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It would be great if you could provide maven artifacts for these projects.
 Flex-mojos is a good starting point for mavenizing them.

Original issue reported on code.google.com by mohammed...@gmail.com on 29 Sep 2008 at 5:47

GoogleCodeExporter commented 9 years ago 
I am open to this if someone wants to volunteer to do the work.

Original comment by mikechambers on 6 Nov 2008 at 9:00

GoogleCodeExporter commented 9 years ago 
Here's what is required: Run this command:

mvn deploy:deploy-file \
    -Dfile=as3corelib.swc \
    -Durl=file:///path/to/some/repo \
    -DgroupId=com.adobe \
    -DartifactId=as3corelib \
    -Dversion=0.92 \
    -Dpackaging=swc

What this does is to deploy the as3corelib.swc file to /path/to/some/repo 
(using the
groupId, artifactId, version). After this if /path/to/some/repo is exposed on 
the
web, users will be able to refer to that web URL (by defining a repository in 
their
Maven project) and use as3corelib as a dependency in their Maven projects.

Temporary work around is for users to install the file into their local Maven 
repository:

mvn install:install-file \
    -Dfile=as3corelib.swc \
    -DgroupId=com.adobe \
    -DartifactId=as3corelib \
    -Dversion=0.92 \
    -Dpackaging=swc \
    -DgeneratePom=true \
    -DcreateChecksum=true

Original comment by aru...@gmail.com on 9 Nov 2008 at 4:04

GoogleCodeExporter commented 9 years ago 
Some Google Code projects use a portion of the SVN tree itself for the Maven
repository since it's already accessible on the web. For example:
  http://flex-mojos.googlecode.com/svn/trunk/repository/
is a Maven repository.

Original comment by aru...@gmail.com on 9 Nov 2008 at 4:07

GoogleCodeExporter commented 9 years ago 
there are two choices here = one is to use the flex-mojos project to use maven 
to 
build the project or as arun here says, which I feel is a much better option, 
is to 
deploy the final artifacts into the repository.  

it is imperative for you guys to come up with the group id and artifact ids, 
for the 
project.

Original comment by mohammed...@gmail.com on 9 Nov 2008 at 12:01

GoogleCodeExporter commented 9 years ago 
BTW I noticed that this project is using Ant for the build. There are some 
Maven Ant
tasks available:
  http://maven.apache.org/ant-tasks/index.html
Specifically the deploy task can be used in this project's build.xml:
  http://maven.apache.org/ant-tasks/reference.html#install

Original comment by aru...@gmail.com on 9 Nov 2008 at 1:54