Grzegorz Kossakowski wrote:
Vadim Gritsenko pisze:
Grzegorz Kossakowski wrote:
I wanted to know what are our rules. Do we:
- want to have such a internal releases
I'd avoid using word release for this as it has some legal
implications and we would get chewed up for using it :)
Ah,
Grzegorz Kossakowski wrote:
I don't think it's harder with Maven. Maven was important factor when it
comes to ability to have independent release cycles. We just need to
clearly define terms (like release) we use
I hope you are not suggesting to stop releasing milestones.
and get used to
Ralph Goers pisze:
I have always been unhappy that Cocoon releases contained non-released
jars for a few reasons:
1. Often the jars were labeled something like xyz-20070525-dev.jar.
It is impossible to download the source for this and know for sure
that it matches what the jar was
Grzegorz Kossakowski wrote:
On the other hand, milestones are just
our internal releases and I think we can live with these gaps.
No, they are not internal:
http://cocoon.apache.org/2.1/changes.html
http://archive.apache.org/dist/cocoon/SOURCES/
Vadim Gritsenko pisze:
Grzegorz Kossakowski wrote:
On the other hand, milestones are just our internal releases and I
think we can live with these gaps.
No, they are not internal:
http://cocoon.apache.org/2.1/changes.html
http://archive.apache.org/dist/cocoon/SOURCES/
Grzegorz Kossakowski wrote:
Vadim Gritsenko pisze:
Grzegorz Kossakowski wrote:
On the other hand, milestones are just our internal releases and I
think we can live with these gaps.
No, they are not internal:
http://cocoon.apache.org/2.1/changes.html
Vadim Gritsenko pisze:
I wanted to know what are our rules. Do we:
- want to have such a internal releases
I'd avoid using word release for this as it has some legal
implications and we would get chewed up for using it :)
Ah, I'm young committer so forgive me that I omit legal implications
Grzegorz Kossakowski wrote:
Examples you provided do not apply to the situation I want to discuss.
In 2.1 times we were shipping all dependencies ourselves so there is
no problem of dependency resolution.
I was talking about the situation when we want to release some early
alpha that has
Torsten Curdt pisze:
3. We cannot put milestones that depend on snapshot versions on
central. It means that we can't upload following artifacts:
org.apache.cocoon:cocoon-maven-plugin:1.0.0-M1
org.apache.cocoon:cocoon-rcl-spring-reloader:1.0.0-M1
Grzegorz Kossakowski wrote:
Even though I agree that it's the best to release all of our
dependencies I would like to know your opinion on how to handle cases
when not all our dependencies are on central server. I'm going to play
with profiles.xml file and see how it performs for us. I would
Reinhard Poetz pisze:
Grzegorz Kossakowski wrote:
Even though I agree that it's the best to release all of our
dependencies I would like to know your opinion on how to handle cases
when not all our dependencies are on central server. I'm going to play
with profiles.xml file and see how it
Hello,
I talked with Maven developers on IRC today. I asked for the problem[1] we are currently facing. They give me interesting advices and
thoughts that may interest you. I paste cleaned up log file of the talk:
[15:32:18] grek hi, I'm Grzegorz Kossakowski, a member of PMC of Apache Cocoon
3. We cannot put milestones that depend on snapshot versions on
central. It means that we can't upload following artifacts:
org.apache.cocoon:cocoon-maven-plugin:1.0.0-M1
org.apache.cocoon:cocoon-rcl-spring-reloader:1.0.0-M1
org.apache.cocoon:cocoon-rcl-webapp-wrapper:1.0.0-M1
If there are
13 matches
Mail list logo
