You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Paul Libbrecht <pa...@activemath.org> on 2004/12/19 00:16:04 UTC
[jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Hi,
I thought there was an automatic communication between the Gump runs
and the ibiblio repository ?
In any cases, currently, the state of the build at
http://brutus.apache.org/gump/public/jakarta-commons/commons-jelly/
is success but the jar on
http://www.ibiblio.org/maven/commons-jelly/jars/ seems to be of
september and the last file there is RC1!
Who can explain or help on this ?
thanks
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Dion Gillard wrote:
>
> Uh, that's what we're doing with Jelly. We're almost at 1.0. We've had
> a release candidate, have one open issue to go before claiming a 1.0
> release.
[Embarrassed] Please forgive me, yes.
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Posted by Dion Gillard <di...@gmail.com>.
On Sun, 19 Dec 2004 18:06:00 -0500, Mark R. Diggory
<md...@latte.harvard.edu> wrote:
>
>
> This really sounds to me like Jelly needs a more aggressive release
> schedule, way too many "betas". I suspect many of these betas could have
> been versions in their own right. Just cut the release and get some
> official verisoning going. I feel Math suffered this as well, but Math
> finally made a release thanks primarily to Phil (salute!).
Uh, that's what we're doing with Jelly. We're almost at 1.0. We've had
a release candidate, have one open issue to go before claiming a 1.0
release.
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Brett Porter wrote:
> (continuing the trend of answering two messages in one :)
>
>
>>Sigh, we really suffer with this misnomer over and over again. In Maven
>>"SNAPSHOT" is just a reference to the latest version of an artifact. So,
>>yes, "SNAPSHOT's" are allowed in the ASF repository. What are not
>>allowed are daily or interim builds (which are what people are mistaking
>>"SNAPSHOT" to mean, these go into the developer repo at
>>cvs.apache.org/repository
>
>
> At the moment, a SNAPSHOT link is not updated for releases generally, so I think
> it is safer to not keep them in the ASF repository to avoid confusion.
> Generally, if you are only interested in releases you will specify the actual
> release name. If you are interested in SNAPSHOTs, you'll be interested in
> something newer than the last release.
>
Your right, SNAPSHOT related activity is very much a developer thing,
projects that have this project as a dependency will be dependent on
official versions. So the repository could easily get away without
SNAPSHOT files.
...
>
>>Yes, old snapshots are a problem, jelly releasing versions should be
>>kept up with the Maven versions, It makes sense that when a release of
>>maven occurs it should use the published versions of its dependencies.
>
>
> I assume this is now referring to Maven 1.0 using a timestamped version of
> Jelly? We might as well rename that timestamp beta-X as it became semi official
> by our use. However, the latest beta of Jelly at the time was not working with
> Maven and not worth the risk to include, and the prior beta was much older.
>
> Maven's HEAD now uses Jelly beta-4 and will use 1.0 when it is out. Most if not
> all of the snapshot dependencies have been removed.
This really sounds to me like Jelly needs a more aggressive release
schedule, way too many "betas". I suspect many of these betas could have
been versions in their own right. Just cut the release and get some
official verisoning going. I feel Math suffered this as well, but Math
finally made a release thanks primarily to Phil (salute!).
>
>>I suspect that this makes sense for gump as long as interim releases are
>>only being used by gump and not by releases. If the Maven build is
>>dependent on an interim release of jelly and it does a release,
>>shouldn't jelly do a release as well to make sure that the appropriate
>>version is used in the release.
>
>
> I think this is unlikely to happen again, but yes - Maven now being up to date
> with Jelly's CVS would push for a release if dependant on any interim release.
>
> - Brett
Hear Hear.
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Posted by Brett Porter <br...@apache.org>.
(continuing the trend of answering two messages in one :)
> Sigh, we really suffer with this misnomer over and over again. In Maven
> "SNAPSHOT" is just a reference to the latest version of an artifact. So,
> yes, "SNAPSHOT's" are allowed in the ASF repository. What are not
> allowed are daily or interim builds (which are what people are mistaking
> "SNAPSHOT" to mean, these go into the developer repo at
> cvs.apache.org/repository
At the moment, a SNAPSHOT link is not updated for releases generally, so I think
it is safer to not keep them in the ASF repository to avoid confusion.
Generally, if you are only interested in releases you will specify the actual
release name. If you are interested in SNAPSHOTs, you'll be interested in
something newer than the last release.
> > Well, I'm worried about others receiving jelly, having downloaded
> > maven... trying to build and run a demo (say "maven demo:swing" in
> > jelly/jelly-tags/swing)... and getting something as bad as a missing
> > method because the snapshot was downloaded from ibiblio and is deadly
> old.
I didn't understand this. Why does someone receive jelly, having downloaded
maven, attempt to run a demo in the Jelly checkout?
Anyway, as you mention later, updating maven.repo.remote in the tag libraries
project properties, or updating the project descriptor to reference the release
that it requires is the right thing to do here.
> Yes, old snapshots are a problem, jelly releasing versions should be
> kept up with the Maven versions, It makes sense that when a release of
> maven occurs it should use the published versions of its dependencies.
I assume this is now referring to Maven 1.0 using a timestamped version of
Jelly? We might as well rename that timestamp beta-X as it became semi official
by our use. However, the latest beta of Jelly at the time was not working with
Maven and not worth the risk to include, and the prior beta was much older.
Maven's HEAD now uses Jelly beta-4 and will use 1.0 when it is out. Most if not
all of the snapshot dependencies have been removed.
> I suspect that this makes sense for gump as long as interim releases are
> only being used by gump and not by releases. If the Maven build is
> dependent on an interim release of jelly and it does a release,
> shouldn't jelly do a release as well to make sure that the appropriate
> version is used in the release.
I think this is unlikely to happen again, but yes - Maven now being up to date
with Jelly's CVS would push for a release if dependant on any interim release.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Posted by "Mark R. Diggory" <md...@latte.harvard.edu>.
Paul Libbrecht wrote:
>
> Le 19 déc. 04, à 00:25, Brett Porter a écrit :
>
>> SNAPSHOT actually shouldn't be there. As far as the ASF repo goes, it
>> has been recommended to use http://cvs.apache.org/repository for
>> SNAPSHOTs and http://www.apache.org/dist/java-repository/ for
>> releases (Which is mirrored to ibiblio).
>
Sigh, we really suffer with this misnomer over and over again. In Maven
"SNAPSHOT" is just a reference to the latest version of an artifact. So,
yes, "SNAPSHOT's" are allowed in the ASF repository. What are not
allowed are daily or interim builds (which are what people are mistaking
"SNAPSHOT" to mean, these go into the developer repo at
cvs.apache.org/repository
commons-jelly-SNAPSHOT.jar is fine in ASF repo as long as it points at
an official release.
>
> I see no recent snapshots there.
> Do I understand, however, that this is the way to go in the future ?
> I'm a bit surprised but maybe I have skipped reading something.
>
>> As far as Maven goes, we are discussing actually codifying separate
>> repositories for snapshots and releases, but haven't resolved it
>> completely yet. Of course, you are able to do this by picking the
>> appropriate properties depending on the release type, eg:
>> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/plugin-
>> parent/project.properties?rev=116299&view=markup
>> then run
>> maven -Dmaven.repo.list=apachecvs jar:deploy-snapshot
>> for example.
>>
Sounds like a good plan to me.
>> As far as correcting it on ibiblio - it can be updated by dropping it
>> into java-repository, or a decision made to remove it. I'm not sure
>> if deletes are propogated - if not, then we can help you out -
>> probably best to make a "MAVENUPLOAD" JIRA request.
this should work appropriately, it can be a symlink or an actual copy of
the most recent.
> Well, I'm worried about others receiving jelly, having downloaded
> maven... trying to build and run a demo (say "maven demo:swing" in
> jelly/jelly-tags/swing)... and getting something as bad as a missing
> method because the snapshot was downloaded from ibiblio and is deadly old.
Yes, old snapshots are a problem, jelly releasing versions should be
kept up with the Maven versions, It makes sense that when a release of
maven occurs it should use the published versions of its dependencies.
Thus it shouldn't be using any interim or daily builds of Jelly, just a
full release.
> For things to run smoothly, then, we need to change maven.repo.remote
> in project.properties (for example in jelly-swing's project.properties)
> after having made sure that the gump nightly goes on this snapshot.
>
> Is this correct ?
>
I suspect that this makes sense for gump as long as interim releases are
only being used by gump and not by releases. If the Maven build is
dependent on an interim release of jelly and it does a release,
shouldn't jelly do a release as well to make sure that the appropriate
version is used in the release.
-Mark
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Posted by Paul Libbrecht <pa...@activemath.org>.
Le 19 déc. 04, à 00:25, Brett Porter a écrit :
> SNAPSHOT actually shouldn't be there. As far as the ASF repo goes, it
> has been recommended to use http://cvs.apache.org/repository for
> SNAPSHOTs and http://www.apache.org/dist/java-repository/ for releases
> (Which is mirrored to ibiblio).
I see no recent snapshots there.
Do I understand, however, that this is the way to go in the future ?
I'm a bit surprised but maybe I have skipped reading something.
> As far as Maven goes, we are discussing actually codifying separate
> repositories for snapshots and releases, but haven't resolved it
> completely yet. Of course, you are able to do this by picking the
> appropriate properties depending on the release type, eg:
> http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/plugin-
> parent/project.properties?rev=116299&view=markup
> then run
> maven -Dmaven.repo.list=apachecvs jar:deploy-snapshot
> for example.
>
> As far as correcting it on ibiblio - it can be updated by dropping it
> into java-repository, or a decision made to remove it. I'm not sure if
> deletes are propogated - if not, then we can help you out - probably
> best to make a "MAVENUPLOAD" JIRA request.
Well, I'm worried about others receiving jelly, having downloaded
maven... trying to build and run a demo (say "maven demo:swing" in
jelly/jelly-tags/swing)... and getting something as bad as a missing
method because the snapshot was downloaded from ibiblio and is deadly
old.
For things to run smoothly, then, we need to change maven.repo.remote
in project.properties (for example in jelly-swing's project.properties)
after having made sure that the gump nightly goes on this snapshot.
Is this correct ?
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [jelly] commons-jelly-SNAPSHOT.jar on ibilio is old ?
Posted by Brett Porter <br...@apache.org>.
Paul Libbrecht wrote:
>
> Hi,
>
> I thought there was an automatic communication between the Gump runs
> and the ibiblio repository ?
Nope
> In any cases, currently, the state of the build at
> http://brutus.apache.org/gump/public/jakarta-commons/commons-jelly/
> is success but the jar on
> http://www.ibiblio.org/maven/commons-jelly/jars/ seems to be of
> september and the last file there is RC1!
>
> Who can explain or help on this ?
SNAPSHOT actually shouldn't be there. As far as the ASF repo goes, it
has been recommended to use http://cvs.apache.org/repository for
SNAPSHOTs and http://www.apache.org/dist/java-repository/ for releases
(Which is mirrored to ibiblio).
As far as Maven goes, we are discussing actually codifying separate
repositories for snapshots and releases, but haven't resolved it
completely yet. Of course, you are able to do this by picking the
appropriate properties depending on the release type, eg:
http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/plugin-parent/project.properties?rev=116299&view=markup
then run
maven -Dmaven.repo.list=apachecvs jar:deploy-snapshot
for example.
As far as correcting it on ibiblio - it can be updated by dropping it
into java-repository, or a decision made to remove it. I'm not sure if
deletes are propogated - if not, then we can help you out - probably
best to make a "MAVENUPLOAD" JIRA request.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org