Hi Neeraj,

You have obviously spent a great deal of time working with the code and it's really good to see how far it's come in this short time.

Someone who checked out trunk would find the pom.xml and know that it's a mvn project. And would just run mvn to get the default goal. Without getting totally lost in the details, maybe it would help newcomers to have something like this:

If you run mvn from trunk, it by default runs the help goal that gives you a help menu that lists the mvn goals that you might want:

mvn runtime
mvn editor
mvn eclipse
mvn all

or something that makes sense to a user.

With regard to how to use mvn, I am also frequently confounded. A message to the maven-user community is often helpful.

Craig

On Jan 15, 2008, at 12:08 PM, Neeraj Joshi wrote:

Hi Craig,
Let me explain the changes I made to the build and then I'll explain the
rationale

1. I added a javaspl_runtime_pom.xml with only the runtime modules listed
in it
2. I modified the original pom.xml to have the editor modules (in addition
to the runtime)
3. I updated the build.xml to have 2 targets a) To build everything b) To
build the runtime only (default)

My goal here was to allow people to build the runtime without forcing the
people to build the editor also.
So when you ran mvn from the trunk I think it used the pom.xml which lists all the modules and the build failed as the repository hadn't been primed
up for eclipse.

One possible solution would be to switch the names so that the default
pom.xml only has the runtime modules and then mvn command from trunk would
work

For the editor build
1. After struggling a while with using maven for eclipse feature building, I figured I would adapt our original ANT build to work with the MAVEN (I
am hoping the community will help out
with a maven only solution)
2. I use maven to compile the src part of the eclipse plugins and then I
use the driver ANT build to package the files the way eclipse needs.
3. In order to make maven build the plugin src the prereq eclipse plugins
need to be added to the maven repository hence the need to run that
command in my previous mail
4. Regarding the need to have an ANTLR variable set. The generated plugin
package needs to have the antlr.jar I have seen some maven mojos to
download all prereqs but I
didn't want to do that as it would bring the rest of the eclipse jars down
also.
I could potentially do that and later delete all but antlr if thats
acceptable?

Suggestions/Comments?

Thanks
Neeraj


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Those are my principles. If you don't like them I have others."

http://incubator.apache.org/imperius

Neeraj Joshi
Autonomic Computing Policy Development
Tivoli, IBM

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Craig L Russell <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/15/2008 02:43 PM
Please respond to
imperius-dev@incubator.apache.org


To
imperius-dev@incubator.apache.org
cc

Subject
Re: Eclipse Editor for SPL checked in






Hi Neeraj,

On Jan 15, 2008, at 11:14 AM, Neeraj Joshi wrote:

Hi Erik,

Actually, it's Craig with the problem.

Couple of things
1) Are you just building the samples modules or the whole thing?

I just did this:

"I tried to build the samples by cd imperius/trunk; mvn and got this:"


2) Not sure if you looked at the build instructions for the editor
on the
website but basically you need to do the following:

No, I didn't read any build instructions. I just did a mvn build from
the trunk.


a.      First configure the maven repository with eclipse plugins.
To do
this on a command prompt run mvn eclipse:make-artifacts -
DeclipseDir= <
ECLIPSE_HOME >

Is there a reason this mvn goal isn't declared as a mvn dependency?

b.      Make sure ANTLR_HOME is set

If ANTLR is a dependency, it should be available via mvn directly. I
don't have any problems with ANTLR in other projects (or in this one
either).

Craig

c.      Run ant all to build both the runtime and the site


Atleast from the error that I see in your email it seems like the
eclipse
platform maven repository artifact does not exist

Let me know if that doesn't resolve the issue
Thanks
Neeraj


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Those are my principles. If you don't like them I have others."

http://incubator.apache.org/imperius

Neeraj Joshi
Autonomic Computing Policy Development
Tivoli, IBM

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Craig L Russell <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/15/2008 01:57 PM
Please respond to
imperius-dev@incubator.apache.org


To
imperius-dev@incubator.apache.org
cc

Subject
Re: Eclipse Editor for SPL checked in






Erik,

As Neeraj points out, your messages are not getting through.

Neeraj,

I tried to build the samples by cd imperius/trunk; mvn and got this:

[INFO] Building jar: /Users/clr/apache/imperius/trunk/javaspl- samples/
target/javaspl-samples-1.0.0-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing /Users/clr/apache/imperius/trunk/javaspl-samples/
target/javaspl-samples-1.0.0-SNAPSHOT.jar to /Users/clr/.m2/
repository/
imperius/javaspl-samples/1.0.0-SNAPSHOT/javaspl-samples-1.0.0-
SNAPSHOT.jar
[INFO]

----------------------------------------------------------------------------
[INFO] Building imperius-spleditorcore
[INFO]    task-segment: [install]
[INFO]

----------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] artifact org.eclipse.platform:org.eclipse.platform: checking
for updates from central
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

No versions are present in the repository for the artifact with a
range [3.3.0,)
 org.eclipse.platform:org.eclipse.platform:jar:null

from the specified remote repositories:
 central (http://repo1.maven.org/maven2)

Craig

On Jan 15, 2008, at 12:15 AM, Erik Bengtson wrote:


--   BlackBerry® from Mobistar    ---

-----Original Message-----
From: Neeraj Joshi <[EMAIL PROTECTED]>

Date: Tue, 15 Jan 2008 02:13:12
To:imperius-dev@incubator.apache.org
Subject: Eclipse Editor for SPL checked in


Hi All,
I have checked in the editor code. I have also updated the website
with
instructions to build and use the editor. Let me know if you face any
problems.
Thanks
Neeraj
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Those are my principles. If you don't like them I have others."

http://incubator.apache.org/imperius

Neeraj Joshi
Autonomic Computing Policy Development
Tivoli, IBM

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/ jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to