You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Poetz <re...@apache.org> on 2006/11/02 07:44:03 UTC
Javaflow/JCI dependencies
tcurdt@apache.org wrote:
> Author: tcurdt
> Date: Wed Nov 1 15:44:11 2006
> New Revision: 470141
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=470141
> Log:
> committed work from Maurizio Pillitu to restore javaflow and class reloading functionality (hurray!!),
:-)
> introduced two SNAPSHOT dependencies that are in NO repository yet!!! (to compile you need to compile jci and javaflow trunk ...will try to fix that soon ...or whoever has more time to fix that),
How can we fix that? I guess we need a release of jci and javaflow, right? Are
you (we) allowed to do releases of _sandboxed_ Jakarta commons projects at all?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: Javaflow/JCI dependencies
Posted by Carsten Ziegeler <cz...@apache.org>.
Can someone PLEASE either add these dependencies to a reachable
repository or uncomment the stuff. This blocks everyone trying to do
some development on Cocoon as event cocoon-bootstrap is not compilable.
Thanks
Carsten
Torsten Curdt schrieb:
>>> introduced two SNAPSHOT dependencies that are in NO repository yet!!! (to compile you need to compile jci and javaflow trunk ...will try to fix that soon ...or whoever has more time to fix that),
>> How can we fix that? I guess we need a release of jci and javaflow, right?
>
> Well, that would be the best case. But for javaflow I am waiting for a
> proper working surefire plugin as the testcase are only working from
> within eclipse. (surefire does not like the classloader stuff in the
> tests) ...while we still have a few improvements to get fixed in
> javaflow I think the interfaces are stable and we could do a release
> and fix the outstanding things in the next release.
>
> For jci that's a different story. I have been wasting most of my time
> with the build setup - which is no fun ...and I am still not happy.
> There are changes (even on the interfaces) required in order to fix an
> eclipse compiler bug and support dependency aware removal of classes.
> ...so there is a bit more that needs to be fixed. But there are
> already a few projects waiting for a release (sorry!)
>
>> Are
>> you (we) allowed to do releases of _sandboxed_ Jakarta commons projects at all?
>
> No ...that requires a vote from the jakarta PMC ....the only thing we
> could do is get a snaphot out into a repository ...or get some people
> help over in jakarta land (hint!) ;-)
>
> cheers
> --
> Torsten
>
--
Carsten Ziegeler - Chief Architect
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: Javaflow/JCI dependencies
Posted by Jorg Heymans <jh...@apache.org>.
Torsten Curdt wrote:
>
> No ...that requires a vote from the jakarta PMC ....the only thing we
> could do is get a snaphot out into a repository ...or get some people
> help over in jakarta land (hint!) ;-)
I installed a snapshot version of both jci and javaflow trunk to
m2-snapshot-repository, cocoon is now building again.
I had to make a few small adjustments to the poms, they didn't deploy
correctly otherwise.
Javaflow needed a change in <distributionManagement> :
Index: pom.xml
===================================================================
--- pom.xml (revision 470478)
+++ pom.xml (working copy)
@@ -117,7 +117,7 @@
<snapshotRepository>
<id>apache-maven-snapshot</id>
<name>repository</name>
-
<url>scpexe://people.apache.org/www/people.apache.org/maven-snapshot-repository</url>
+
<url>scpexe://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
</snapshotRepository>
<site>
<id>website</id>
JCI needed a few version changes as well :
Index: pom.xml
===================================================================
--- pom.xml (revision 470285)
+++ pom.xml (working copy)
@@ -59,12 +59,13 @@
<name>repository</name>
<url>scpexe://people.apache.org/x1/www/people.apache.org/maven-snapshot-repository</url>
</repository>
+-->
<snapshotRepository>
<id>apache-maven-snapshot</id>
<name>repository</name>
-
<url>scpexe://people.apache.org/x1/www/people.apache.org/maven-snapshot-repository</url>
+
<url>scpexe://people.apache.org/www/people.apache.org/repo/m2-snapshot-repository</url>
</snapshotRepository>
--->
+
<site>
<id>website</id>
<url>scpexe://people.apache.org/www/jakarta.apache.org/commons/sandbox/jci</url>
Index: compilers/eclipse/pom.xml
===================================================================
--- compilers/eclipse/pom.xml (revision 470285)
+++ compilers/eclipse/pom.xml (working copy)
@@ -15,7 +15,7 @@
<groupId>org.apache.commons</groupId>
<artifactId>commons-jci-eclipse</artifactId>
- <version>3.2.0.658</version>
+ <version>1.0-SNAPSHOT</version>
<name>compiler-eclipse</name>
Index: compilers/groovy/pom.xml
===================================================================
--- compilers/groovy/pom.xml (revision 470285)
+++ compilers/groovy/pom.xml (working copy)
@@ -15,7 +15,7 @@
<groupId>org.apache.commons</groupId>
<artifactId>commons-jci-groovy</artifactId>
- <version>1.0-jsr-03</version>
+ <version>1.0-SNAPSHOT</version>
<name>compiler-groovy</name>
Index: compilers/janino/pom.xml
===================================================================
--- compilers/janino/pom.xml (revision 470285)
+++ compilers/janino/pom.xml (working copy)
@@ -15,7 +15,7 @@
<groupId>org.apache.commons</groupId>
<artifactId>commons-jci-janino</artifactId>
- <version>2.4.1</version>
+ <version>1.0-SNAPSHOT</version>
<name>compiler-janino</name>
Re: Javaflow/JCI dependencies
Posted by Torsten Curdt <tc...@apache.org>.
> > introduced two SNAPSHOT dependencies that are in NO repository yet!!! (to compile you need to compile jci and javaflow trunk ...will try to fix that soon ...or whoever has more time to fix that),
>
> How can we fix that? I guess we need a release of jci and javaflow, right?
Well, that would be the best case. But for javaflow I am waiting for a
proper working surefire plugin as the testcase are only working from
within eclipse. (surefire does not like the classloader stuff in the
tests) ...while we still have a few improvements to get fixed in
javaflow I think the interfaces are stable and we could do a release
and fix the outstanding things in the next release.
For jci that's a different story. I have been wasting most of my time
with the build setup - which is no fun ...and I am still not happy.
There are changes (even on the interfaces) required in order to fix an
eclipse compiler bug and support dependency aware removal of classes.
...so there is a bit more that needs to be fixed. But there are
already a few projects waiting for a release (sorry!)
> Are
> you (we) allowed to do releases of _sandboxed_ Jakarta commons projects at all?
No ...that requires a vote from the jakarta PMC ....the only thing we
could do is get a snaphot out into a repository ...or get some people
help over in jakarta land (hint!) ;-)
cheers
--
Torsten