You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Adam Lally <al...@alum.rpi.edu> on 2007/08/06 23:41:18 UTC

Put Maven artifacts up for vote too?

As I recall we had a couple of user requests for us to publish our
jars as Maven artifacts in the Apache incubator repository.  And I
think I got our Maven metadata into shape during the 2.1.0 release
process after some comments from Dan Kulp on the general@i.a.o list.

So should we put these up for a vote as well?

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Michael Baessler <mb...@michael-baessler.de>.
Adam Lally wrote:
> As I recall we had a couple of user requests for us to publish our
> jars as Maven artifacts in the Apache incubator repository.  And I
> think I got our Maven metadata into shape during the 2.1.0 release
> process after some comments from Dan Kulp on the general@i.a.o list.
>
> So should we put these up for a vote as well?
>
> -Adam
>
>
>   
+1

-- Michael

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/8/07, Marshall Schor <ms...@schor.com> wrote:
> Reading the above link - it specifies "requirements" for the pom file
> for things going into
> the Maven repository, which our POM doesn't have.  2 I found missing
> were the
> <license> and the <scm> elements.
>

Good catch - I will add these right away.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Marshall Schor <ms...@schor.com>.
Adam Lally wrote:
> On 8/7/07, Adam Lally <al...@alum.rpi.edu> wrote:
>   
>> Maven automatically generates "sources" jar files (check your local
>> Maven repository).  Unfortunately these don't have the DISCLAIMER,
>> LICENSE, NOTICES.  I will see if I can figure out how to get those to
>> be added.
>>
>>     
>
> I've fixed this in SVN (see UIMA-521).
>
> The command to get maven to generate the source jars is:
> mvn source:jar
>
> This page describes how to create bundles to upload to a repository:
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html
>
>   
Reading the above link - it specifies "requirements" for the pom file 
for things going into
the Maven repository, which our POM doesn't have.  2 I found missing 
were the
<license> and the <scm> elements. 

-Marshall
> -Adam
>
>
>   


Re: Put Maven artifacts up for vote too?

Posted by Marshall Schor <ms...@schor.com>.
Adam Lally wrote:
> On 8/8/07, Marshall Schor <ms...@schor.com> wrote:
>   
>> I've found some places in Apache docs where it seems to be true that the
>> Maven artifacts themselves,
>> do need to be signed.  One of these is the ref to releasing "Struts",
>> found here:
>> http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
>>
>> see step 6 and 7.
>> <snip/>
>>     
>
> Yes, looks like they are typically signed.
>
> I just committed a change to the uimaj pom that will cause the
> artifacts to be signed when the "mvn deploy" task is run.  You need to
> first install gpg and create a key as described in:
> http://incubator.apache.org/uima/distribution.html.
>   
Great!  You are a true Maven maven :-)  -Marshall



Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/8/07, Marshall Schor <ms...@schor.com> wrote:
> I've found some places in Apache docs where it seems to be true that the
> Maven artifacts themselves,
> do need to be signed.  One of these is the ref to releasing "Struts",
> found here:
> http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html
>
> see step 6 and 7.
> <snip/>

Yes, looks like they are typically signed.

I just committed a change to the uimaj pom that will cause the
artifacts to be signed when the "mvn deploy" task is run.  You need to
first install gpg and create a key as described in:
http://incubator.apache.org/uima/distribution.html.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Marshall Schor <ms...@schor.com>.
Adam Lally wrote:
> On 8/8/07, Thilo Goetz <tw...@gmx.de> wrote:
>   
>> Sure, that would be good.  I'm currently building a new level, I'll
>> create the maven artifacts manually for this one.
>>
>>     
>
> I'm actually having some trouble at the moment... For one thing mvn
> repository:bundle-create fails when I run it on the root uimaj
> project, basically because this project doesn't have any artifact
> associated with it.  Of course it would be nice if it would build the
> artifacts for the sub-projects...
>
> Next issue is that running it on uimaj-core complains about missing
> fields in the POM, which I'm looking into.  This may be a good thing
> that it's catching.
>
>   
>> One more question: I assume that the mvn artifacts do not need to
>> be signed, at least I didn't see anything about that.  Is that your
>> understanding also?
>>
>>     
>
> I think that is correct.
>   
Adam's done a great deal of work getting this Maven thing to go - Thanks!

I've found some places in Apache docs where it seems to be true that the 
Maven artifacts themselves,
do need to be signed.  One of these is the ref to releasing "Struts", 
found here:
http://struts.apache.org/2.x/docs/creating-and-signing-a-distribution.html

see step 6 and 7.

Next, see http://www.apache.org/dev/release-publishing.html
which, while not specific to Maven, seems to indicate the need to sign 
individual Jars, etc.

Also, http://mina.apache.org/developer-guide.html in step 2 uses
gpg-sign-all script to sign all the jars.

Some of the jar signing I saw seemed to be of a different ilk than gpg 
signing.
Do you know how the Jar signing described in
http://java.sun.com/docs/books/tutorial/deployment/jar/signindex.html
relates to the gpg signing?

-Marshall

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/9/07, Thilo Goetz <tw...@gmx.de> wrote:
> I spent a long time today trying to get ssh configured to login
> using PKI: I give up, I don't want to spend more time on this.
> Can I just upload those artifacts manually, or does maven do
> any magic while it's doing that?
>
> --Thilo
>

I don't know for sure, but probably you can upload them from your
local Maven repository.

For me everything worked just having Putty and Pageant installed, the
way that I was originally logging into people.apache.org.  I just had
to set my maven settings.xml file to point at my private key, and have
Pageant running.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Thilo Goetz <tw...@gmx.de>.
I spent a long time today trying to get ssh configured to login
using PKI: I give up, I don't want to spend more time on this.
Can I just upload those artifacts manually, or does maven do
any magic while it's doing that?

--Thilo

Adam Lally wrote:
> On 8/8/07, Adam Lally <al...@alum.rpi.edu> wrote:
>> I will try to add a -deploy option to extractAndBuild script which
>> will execute this, and I plan to (eventually) put this information on
>> the Wiki "Instructions for Committers" page.
>>
> 
> Done and done.  Instructions are here:
> http://cwiki.apache.org/confluence/display/UIMA/Deploying+Maven+Artifacts+to+the+Staging+Repository
> 
> I think we're ready to give this a shot for a real release candidate.
> 
> -Adam (trying to set the record for most times consecutively replying
> to oneself in an email thread :)

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/8/07, Adam Lally <al...@alum.rpi.edu> wrote:
> I will try to add a -deploy option to extractAndBuild script which
> will execute this, and I plan to (eventually) put this information on
> the Wiki "Instructions for Committers" page.
>

Done and done.  Instructions are here:
http://cwiki.apache.org/confluence/display/UIMA/Deploying+Maven+Artifacts+to+the+Staging+Repository

I think we're ready to give this a shot for a real release candidate.

-Adam (trying to set the record for most times consecutively replying
to oneself in an email thread :)

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
OK, I think I've gotten deployment of our Maven artifacts to a
"staging repository" to work.  I committed a change to the uimaj
pom.xml:

  <distributionManagement>
    <repository>
      <id>staging-repository</id>
     <url>
        scpexe://people.apache.org/home/alally/public_html/uima-2.2.0-incubating/maven/
     </url>
    </repository>
  </distributionManagement>

This URL indicates the location of the repository.  We can continue to
use my public_html directory, or Thilo could change this to his to be
consistent with the locations of the distribution files, it doesn't
matter to me.  I already did one deployment, you can see what it looks
like here:
http://people.apache.org/~alally/uima-2.2.0-incubating/maven


The maven command to run (from the uimaj directory) to do the deployment is:
mvn source:jar deploy

Note that, for Windows, in order to do a deployment you also have to
update your Maven settings.xml file to indicate your ssh client.  For
me, this file is in Document And Settings/Administrator/.m2.  I added
the following stanza:
<servers>
    <server>
      <id>staging-repository</id>
      <username>alally</username>
      <privateKey>c:/alally/keys/alally.ppk</privateKey>
      <configuration>
        <sshExecutable>plink</sshExecutable>
        <scpExecutable>pscp</scpExecutable>
      </configuration>
    </server>
</servers>

which works if you have putty installed (be sure to point at your own
privateKey file though).  I got the instructions from here:
http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh-external.html

I will try to add a -deploy option to extractAndBuild script which
will execute this, and I plan to (eventually) put this information on
the Wiki "Instructions for Committers" page.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
Next problem is that mvn repository:bundle-create complains about a
missing LICENSE.txt file.  What's that about!?

Looking in incubator general for other projects that asked the IPMC to
ratify their maven artifacts, it looks like the preferred approach is
to set up a "staging" repository in somebody's public-html directory,
and deploy the artifacts there.

The site http://maven.apache.org/guides/mini/guide-central-repository-upload.html
does indicate that this is preferred to the manual update process.

I will try to get this to work.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/8/07, Thilo Goetz <tw...@gmx.de> wrote:
> Sure, that would be good.  I'm currently building a new level, I'll
> create the maven artifacts manually for this one.
>

I'm actually having some trouble at the moment... For one thing mvn
repository:bundle-create fails when I run it on the root uimaj
project, basically because this project doesn't have any artifact
associated with it.  Of course it would be nice if it would build the
artifacts for the sub-projects...

Next issue is that running it on uimaj-core complains about missing
fields in the POM, which I'm looking into.  This may be a good thing
that it's catching.

> One more question: I assume that the mvn artifacts do not need to
> be signed, at least I didn't see anything about that.  Is that your
> understanding also?
>

I think that is correct.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Thilo Goetz <tw...@gmx.de>.
Adam Lally wrote:
> On 8/8/07, Thilo Goetz <tw...@gmx.de> wrote:
>> Adam Lally wrote:
>>> This page describes how to create bundles to upload to a repository:
>>> http://maven.apache.org/guides/mini/guide-central-repository-upload.html
>> Sorry, but I'm not sure how we're going to proceed now.  What
>> exactly are the artifacts we're going to vote on, and who
>> is going to create them?  Do we proceed with the main release
>> and do the mvn stuff separately, or all in one fell swoop
>> (my inclination would be the latter)?
>>
> 
> All in one fell swoop would be my preference too.
> 
> I think we run the mvn source:jar and repository:bundle-create
> commands like it says on that page I linked to above.  It says: "The
> bundle will be created in your target directory with the name:
> $pom.artifactId-$pom.currentVersion-bundle.jar"
> 
> Then we include these jars among our artifacts that we (and the IPMC) vote on.
> 
> Maybe these maven commands should be added to the extractAndBuild
> script so that these are always built along with the other release
> artifacts?  I can do that and test that it works for me, then maybe
> you can run the actual build for the next release candidate?
> 
> -Adam

Sure, that would be good.  I'm currently building a new level, I'll
create the maven artifacts manually for this one.

One more question: I assume that the mvn artifacts do not need to
be signed, at least I didn't see anything about that.  Is that your
understanding also?

--Thilo

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/8/07, Thilo Goetz <tw...@gmx.de> wrote:
> Adam Lally wrote:
> > This page describes how to create bundles to upload to a repository:
> > http://maven.apache.org/guides/mini/guide-central-repository-upload.html
>
> Sorry, but I'm not sure how we're going to proceed now.  What
> exactly are the artifacts we're going to vote on, and who
> is going to create them?  Do we proceed with the main release
> and do the mvn stuff separately, or all in one fell swoop
> (my inclination would be the latter)?
>

All in one fell swoop would be my preference too.

I think we run the mvn source:jar and repository:bundle-create
commands like it says on that page I linked to above.  It says: "The
bundle will be created in your target directory with the name:
$pom.artifactId-$pom.currentVersion-bundle.jar"

Then we include these jars among our artifacts that we (and the IPMC) vote on.

Maybe these maven commands should be added to the extractAndBuild
script so that these are always built along with the other release
artifacts?  I can do that and test that it works for me, then maybe
you can run the actual build for the next release candidate?

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Thilo Goetz <tw...@gmx.de>.
Adam Lally wrote:
> On 8/7/07, Adam Lally <al...@alum.rpi.edu> wrote:
>> Maven automatically generates "sources" jar files (check your local
>> Maven repository).  Unfortunately these don't have the DISCLAIMER,
>> LICENSE, NOTICES.  I will see if I can figure out how to get those to
>> be added.
>>
> 
> I've fixed this in SVN (see UIMA-521).
> 
> The command to get maven to generate the source jars is:
> mvn source:jar
> 
> This page describes how to create bundles to upload to a repository:
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html
> 
> -Adam

Sorry, but I'm not sure how we're going to proceed now.  What
exactly are the artifacts we're going to vote on, and who
is going to create them?  Do we proceed with the main release
and do the mvn stuff separately, or all in one fell swoop
(my inclination would be the latter)?

--Thilo

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/7/07, Adam Lally <al...@alum.rpi.edu> wrote:
> Maven automatically generates "sources" jar files (check your local
> Maven repository).  Unfortunately these don't have the DISCLAIMER,
> LICENSE, NOTICES.  I will see if I can figure out how to get those to
> be added.
>

I've fixed this in SVN (see UIMA-521).

The command to get maven to generate the source jars is:
mvn source:jar

This page describes how to create bundles to upload to a repository:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/7/07, Marshall Schor <ms...@schor.com> wrote:
> OK with me.  I verified that in at least one Jar (and Adam should
> confirm the build does this
> for all Jars) there are the following files in the META-INF directory:
>
>    DISCLAIMER
>    LICENSE
>    NOTICES
>

I check that these files are in all of the jars.

For the Eclipse plugins, though, the DISCLAIMER, LICENSE, and NOTICE
files are in the jars that are inside the plugin zip files, but they
aren't in the META-INF directory of the plugins themselves.  That
might be a problem.


> Maven has a the ability to download "sources" as well from the
> repository, for Eclipse:
>
> |mvn -Declipse.downloadSources=true|
>
> This tells maven to download all associated sources of jar files in the
> pom.xml. Amazing, how much easier it is to set up a project with proper
> debugging sources etc.
>
> Do we need to do something to "enable" this to work?
>

Maven automatically generates "sources" jar files (check your local
Maven repository).  Unfortunately these don't have the DISCLAIMER,
LICENSE, NOTICES.  I will see if I can figure out how to get those to
be added.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Marshall Schor <ms...@schor.com>.
Adam Lally wrote:
> As I recall we had a couple of user requests for us to publish our
> jars as Maven artifacts in the Apache incubator repository.  And I
> think I got our Maven metadata into shape during the 2.1.0 release
> process after some comments from Dan Kulp on the general@i.a.o list.
>
> So should we put these up for a vote as well?
>   
OK with me.  I verified that in at least one Jar (and Adam should 
confirm the build does this
for all Jars) there are the following files in the META-INF directory:

   DISCLAIMER
   LICENSE
   NOTICES

which seem necessary for individual Maven-distributed Jars.

Maven has a the ability to download "sources" as well from the 
repository, for Eclipse:

|mvn -Declipse.downloadSources=true|

This tells maven to download all associated sources of jar files in the 
pom.xml. Amazing, how much easier it is to set up a project with proper 
debugging sources etc.

Do we need to do something to "enable" this to work?

-Marshall


Re: Put Maven artifacts up for vote too?

Posted by Adam Lally <al...@alum.rpi.edu>.
On 8/7/07, Thilo Goetz <tw...@gmx.de> wrote:
> Hi Adam,
>
> sure.  Which jars do we want to publish?  All of them, or the core
> jar only?
>

I think all of them.  I'm less certain though about the Eclipse
plugins (where the Maven artifact is a zip, not a jar).  I'll ask on
uima-user in case there are people interested in this who don't also
read uima-dev.

> I also gave up on following the Maven debate on general@i.a.o at some
> point.  What repository are we allowed to deploy to?
>

/www/people.apache.org/repo/m2-incubating-repository

That's according to a note from Dan Kulp 7 days ago on this subject.

-Adam

Re: Put Maven artifacts up for vote too?

Posted by Thilo Goetz <tw...@gmx.de>.
Hi Adam,

sure.  Which jars do we want to publish?  All of them, or the core
jar only?

I also gave up on following the Maven debate on general@i.a.o at some
point.  What repository are we allowed to deploy to?

--Thilo

Adam Lally wrote:
> As I recall we had a couple of user requests for us to publish our
> jars as Maven artifacts in the Apache incubator repository.  And I
> think I got our Maven metadata into shape during the 2.1.0 release
> process after some comments from Dan Kulp on the general@i.a.o list.
> 
> So should we put these up for a vote as well?
> 
> -Adam