Re: How to test?

2010-01-30 Thread Reinhard Pötz
David Legg wrote:
 I thought I'd give C3 a go but I appear to have a couple of artifacts
 missing when I run Maven.  They are: -
 
  com.sun.jersey:jersey-core:jar:1.0.3
  com.sun.jersey:jersey-server:jar:1.0.3
 
 I've tried making sure I'm using the 'cocoon-staging' profile mentioned
 in the email but to no effect.  It is getting late here now but tomorrow
 I'll try manually installing the missing jar files and try again.
 
 The Maven error looks as follows: -
 
 D:\projects\cocoon\cocoon3\mysamplemvn jetty:run -P cocoon-staging
 ...
 [INFO] Failed to resolve artifact.
 ...
 Missing:
 --
 1) com.sun.jersey:jersey-core:jar:1.0.3
 
  Try downloading the file manually from the project website.
 
  Path to dependency:
1) com.mycompany:mysample:jar:1.0-SNAPSHOT
2) com.sun.jersey:jersey-core:jar:1.0.3
 ...
 2) com.sun.jersey:jersey-server:jar:1.0.3
 
  Try downloading the file manually from the project website.
 
  Path to dependency:
1) com.mycompany:mysample:jar:1.0-SNAPSHOT
2) com.sun.jersey:jersey-server:jar:1.0.3
 ...
 --
 2 required artifacts are missing.
 
 for artifact:
  com.mycompany:mysample:jar:1.0-SNAPSHOT
 
 from the specified remote repositories:
  cocoon.staging (http://people.apache.org/builds/cocoon),
  central (http://repo1.maven.org/maven2)

Thanks David! I don't know why this can happen because I built the
release artifacts on a clean machine with an empty Maven repository and
without a Maven proxy.

Anyway, I will create an alpha-3 release in February that will fix this
problem.

-- 
Reinhard Pötz   Managing Director, {Indoqa} GmbH
 http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member  reinh...@apache.org



Re: How to test?

2010-01-30 Thread David Legg


Reinhard Pötz wrote:

David Legg wrote:
  

I thought I'd give C3 a go but I appear to have a couple of artifacts
missing when I run Maven.  They are: -

 com.sun.jersey:jersey-core:jar:1.0.3
 com.sun.jersey:jersey-server:jar:1.0.3


Thanks David! I don't know why this can happen because I built the
release artifacts on a clean machine with an empty Maven repository and
without a Maven proxy.
  


I got it to work as soon as I included the correct jersey maven 
repository addresses in the pom.xml file.  I wrote about it in the 
Cocoon user mail list.


Regards,
David Legg.



Re: How to test?

2010-01-27 Thread David Legg
I thought I'd give C3 a go but I appear to have a couple of artifacts 
missing when I run Maven.  They are: -


 com.sun.jersey:jersey-core:jar:1.0.3
 com.sun.jersey:jersey-server:jar:1.0.3

I've tried making sure I'm using the 'cocoon-staging' profile mentioned 
in the email but to no effect.  It is getting late here now but tomorrow 
I'll try manually installing the missing jar files and try again.


The Maven error looks as follows: -

D:\projects\cocoon\cocoon3\mysamplemvn jetty:run -P cocoon-staging
...
[INFO] Failed to resolve artifact.
...
Missing:
--
1) com.sun.jersey:jersey-core:jar:1.0.3

 Try downloading the file manually from the project website.

 Path to dependency:
   1) com.mycompany:mysample:jar:1.0-SNAPSHOT
   2) com.sun.jersey:jersey-core:jar:1.0.3
...
2) com.sun.jersey:jersey-server:jar:1.0.3

 Try downloading the file manually from the project website.

 Path to dependency:
   1) com.mycompany:mysample:jar:1.0-SNAPSHOT
   2) com.sun.jersey:jersey-server:jar:1.0.3
...
--
2 required artifacts are missing.

for artifact:
 com.mycompany:mysample:jar:1.0-SNAPSHOT

from the specified remote repositories:
 cocoon.staging (http://people.apache.org/builds/cocoon),
 central (http://repo1.maven.org/maven2)


Regards,
David Legg



How to test? (was: [vote] Release Cocoon 3.0.0-alpha-2)

2010-01-04 Thread Reinhard Pötz
(Note: Those instructions require the usage of Maven 2. If you want to
use/test Cocoon without Maven, pls let me know.)

If you already use Cocoon 3 the best way to test is setting the version
to 3.0.0-alpha-2, e.g.:

dependency
  groupIdorg.apache.cocoon.sax/groupId
  artifactIdcocoon-sax/artifactId
  version3.0.0-alpha-2/version
/dependency


If you want to explore how a Cocoon 3 web application works, use the
'Samples Archetype':

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
-DarchetypeGroupId=org.apache.cocoon.archetype-sample
-DarchetypeArtifactId=cocoon-archetype-sample
-DarchetypeVersion=3.0.0-alpha-2 -DgroupId=com.mycompany
-DartifactId=mysample
-DremoteRepositories=http://people.apache.org/builds/cocoon/

Then move into the base directory and run

mvn jetty:run -P cocoon-staging

Make sure that the 'cocoon-staging' profile is set in your
~/.m2/settings.xml:

profile
  idcocoon-staging/id
  repositories
repository
  idcocoon.staging/id
  nameCocoon staging repository/name
  urlhttp://people.apache.org/builds/cocoon/url
/repository
  /repositories
  pluginRepositories
pluginRepository
  idcocoon.staging/id
  nameCocoon staging repository/name
  urlhttp://people.apache.org/builds/cocoon/url
/pluginRepository
  /pluginRepositories
/profile



In order to start a new Cocoon 3 webapp project, use one of the
following archetypes:

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
-DarchetypeGroupId=org.apache.cocoon.archetype-block
-DarchetypeArtifactId=cocoon-archetype-block
-DarchetypeVersion=3.0.0-alpha-2 -DgroupId=com.mycompany
-DartifactId=mysite
-DremoteRepositories=http://people.apache.org/builds/cocoon/

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
-DarchetypeGroupId=org.apache.cocoon.archetype-parent
-DarchetypeArtifactId=cocoon-archetype-parent
-DarchetypeVersion=3.0.0-alpha-2 -DgroupId=com.mycompany
-DartifactId=myparent
-DremoteRepositories=http://people.apache.org/builds/cocoon/

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
-DarchetypeGroupId=org.apache.cocoon.archetype-webapp
-DarchetypeArtifactId=cocoon-archetype-webapp
-DarchetypeVersion=3.0.0-alpha-2 -DgroupId=com.mycompany
-DartifactId=mywebapp
-DremoteRepositories=http://people.apache.org/builds/cocoon/

Again, make sure that you activate the 'cocoon-staging' profile when you
build your project.

One final note, all Cocoon artifacts require Maven 2.0.9 or higher.
Otherwise the transitive dependency resolution of Maven doesn't work
properly.

-- 
Reinhard Pötz   Managing Director, {Indoqa} GmbH
 http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member  reinh...@apache.org