I'm trying to do some simple refactoring of the spec APIs to fix JIRA
909, and running into the following issues:
I am using Eclipse and running mvn -Peclipse eclipse:eclipse in the spec
and sca folders to generate Eclipse projects. If I remember correctly
this used to generate correct
Hi,
I'm not sure that Dan's solution is the best one, I mean running mvn
-Peclipse profile should build eclipse projects already linked between them.
If you open the Configure build path ... of the core project you
should find all the dependencies as connected project in the Projects
Tab. I
that Dan's solution is the best one, I mean running mvn
-Peclipse profile should build eclipse projects already linked between
them.
If you open the Configure build path ... of the core project you
should find all the dependencies as connected project in the Projects
Tab. I think Eclipse uses
this has
been
working for me. Cheers.
Jean-Sebastien Delfino wrote:
I'm trying to do some simple refactoring of the spec APIs to fix JIRA
909, and running into the following issues:
I am using Eclipse and running mvn -Peclipse eclipse:eclipse in the spec
and sca folders to generate Eclipse
-Peclipse eclipse:eclipse in the
spec
and sca folders to generate Eclipse projects. If I remember correctly
this used to generate correct Eclipse project dependencies, for example
the core project had a dependency on the sca-api project. Now project
core depends on the sca-api-r0.95 jar
to generate Eclipse projects. If
I remember correctly
this used to generate correct Eclipse project
dependencies, for example
the core project had a dependency on the sca-api
project. Now project
core depends on the sca-api-r0.95 jar instead.
Code changes that I make
in the sca-api
folders to generate Eclipse projects. If I remember correctly
this used to generate correct Eclipse project dependencies, for
example
the core project had a dependency on the sca-api project. Now project
core depends on the sca-api-r0.95 jar instead. Code changes that I
make
in the sca-api
eclipse:eclipse in the spec
and sca folders to generate Eclipse projects. If
I remember correctly
this used to generate correct Eclipse project
dependencies, for example
the core project had a dependency on the sca-api
project. Now project
Adriano,
Did you generate the eclipse artifacts using the maven build first?
If not, you can generate the .project and .classpath by doing:
mvn -Peclipse eclipse:eclipse
Brent
On 10/16/06, Adriano Crestani [EMAIL PROTECTED] wrote:
I've already downloaded all the source code using the
Once you generate the project files, you should be able to go to eclipse and
do an import : Existing projects into Workspace, and select the directory
you ran mvn -Peclipse eclipse:eclipse. Note that the command will generate
eclipse project files for all projects contained on the sub directory
Further to this, you''l find that the eclipse projects base the locations
of jars that they depend on a variable called M2_REPO,
but that variable is not set. So you'll either need to set this variable
and use maven to install these dependencies into your maven repository, or
you will need
I had tried it, but now I realised that when I executed this command I was
outside the folder java, now I am trying it in folder java and it seems to
be working. Thanks.
Adriano Crestani
On 10/16/06, Luciano Resende [EMAIL PROTECTED] wrote:
Once you generate the project files, you should be
12 matches
Mail list logo
