openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Prud'hommeaux <>
Subject Re: Artifact names
Date Wed, 11 Apr 2007 17:09:00 GMT

I personally think that keeping "-project-" in the artifact zip name  
is tolerable. I too had looked around (albeit briefly) for a solution  
to this a while ago, and found none.

Once OpenJPA is out of incubation and we are deploying releases to  
the Apache mirror system, we'll probably need to put in some more  
deployment-oriented logic that doesn't use the "deploy" phase, so at  
that time we might be able to put in some renaming logic.

+1 for tolerating the artifact name "openjpa-project-0.9.7-".

On Apr 11, 2007, at 8:34 AM, Michael Dick wrote:

> Hi,
> I'm hitting a bit of a snag with the staging repository for release  
> 0.9.7.
> Recently we made changes to remove -project from our the zip file  
> names. The
> problem is that the maven install and deploy goals ignore the names we
> provide and generate their own names (
> I searched through the mailing list archives  
> and it
> turns out this is a fairly common problem - usually resulting in a  
> response
> of "working as designed".  Here's an example
> tf1449780s177.html#a3916784
> Does anyone vehemently object to putting -project back into the  
> names for
> the 0.9.7 release?
> The only other way I know of to fix the names that get deployed  
> would be to
> change the artifactId in the pom files (basically switch openjpa with
> openjpa-project). Switching the names will impact anyone who has a
> dependency on the base openjpa project. They'll have to update the  
> version
> number anyway, but it will still be a little confusing if they used to
> depend on openjpa-0.9.6 and now they depend on openjpa-project-0.9.7.
> Thanks,
> -- 
> -Michael Dick

View raw message