Sarasvati on Maven

[sgw.y]

Hello guys,


Is there a POM available somewhere for the project?
I installed your jars in my local repo myself but would like to get
your input;


Regards

[Paul Lorenz]

Hi Yvan,
   We don't currently have a POM. We currently use a simple ant build process. I would like to see us move to either maven or ivy at some point pre-1.0 release, but it's been lower on the priority list.

If you (or anyone else) has any arguments pro/con maven and/or ivy, I'm happy to hear them. Also, if we want to make life easier for developers who use maven, do we need to convert to maven, or we just need to provide a POM file? If this is the case, and you have a POM file for Sarasvati that you'd like to contribute, that would be great.

Pardon my ignorance, I haven't made the move past ant yet :)

cheers,
Paul

[Cheong Chung Onn]

Here's my take about maven, the learning curve is steep, once we get it
to work it would work great and once it breaks it is very painful. Also
maven doesn't gel well with projects that are not mavenized. In fact I
have to manually create my sarasvati snapshot and deploy it to my
internal maven repository.

I think it is possible to mavenized Sarasvati using existing project
structure however i believe it would be better to follow the proposed
convention. I can give it a try to mavenize Sarasvati using the existing
structure once i managed to find some time - dont hold your breath though.

Regards
chung-onn

[sgw.y]

Hello,

Almost got it working with a basic QuickStart archetype;
The only problem is that some files are missing from the src in the
rc2 package: RubricLexer and RubricParser;

Are they available on svn?

[Cheong Chung Onn]

Hi Yvan,

The Rubric* stuffs are already packaged in jar and is found in
sarasvati-folder/lib/rubric.jar

Hope this helps.

Regards
chung-onn

[Cheong Chung Onn]

Hi Paul,

I just started to explore in mavenizing Sarasvati. It seems inevitable
that project structure needs to be changed. Essentially each module e.g.
src, editor, visual, examples will become a sub-module within Sarasvati
project. This means that "src" will become sarasvati module, "editor"
will become sarasvati-editor, "visual" will become sarasvati-visual -
see below.

The structure of the project will be something like
Sarasvati project (aka. java-workflow)
+sarasvati (aka src)
+sarasvati-visual (aka visual)
+sarasvati-editor (aka editor)
+sarasvati-examples (aka examples)

I think I am 30% done, i wont be commit-ing any of the changes i made to
the project structure till you give the green light. Also i am not
certain if I can get it working even you have given you blessing :(

Regards
chung-onn

Paul Lorenz wrote:

[sgw.y]

I don't have anything but a few script in the lib/ folder
(antlr.license.txt, apache.license.txt, apache-licence-2.0.txt);

Could you check once again or just send these two files per mail
(hoping I won't miss anything else later);

[Paul Lorenz]

Can you do the following: Whenever you want to snapshot your work, just branch your workspace contents to branches/maven-<date>?

That way we can see what you're working on, and you can stay on trunk at the same time. Let me know if that makes sense.

thanks,
Paul

[Paul Lorenz]

If you're using the download, you need to run ant fetchlibs to grab the libraries. However, this probably won't get you rubric.jar, since that jar is only needed during development. I'd recommend checking out the project from trunk.

cheers,
Paul

[Cheong Chung Onn]

I am currently working out the POMs, when they are ready a snapshot as
per suggestion.

[Cheong Chung Onn]

Paul Lorenz wrote:
> Can you do the following: Whenever you want to snapshot your work,
> just branch your workspace contents to branches/maven-<date>?

I have created the pom files and it is commited to the branch -
branches/maven-2009.07.31. I did find there is a circular reference
between src-folder (sarasvati-core) and editor-folder (sarasvati-editor)
as both are referencing the SvUtil. I suggest moving SvUtil#uniqueNames
to a new class/method SvEditorUtil#getUniqueNames to break this circular
reference. Any thought?

Fyi, the nested modules do not contain the source codes as i have
deleted them away. I am thinking of retaining the existing project
structure and doing a symbolic link to the maven modules. I think this
would not work on a windows env also I am not sure how to create a
symbolic in svn.

[Paul Lorenz]

Hi chung-onn,
   Thanks for trying this out. I fixed the circular reference. I just put it back in EditorGraph, since that's the only place it was used.

I hadn't thought of using symlinks. That's a neat idea. Subversion handles symlinks just like regular files, so no problem there. However, you are correct, this will not work on windows. This isn't a large concern for me personally, however, I don't want to discourage developers who work on Windows. On the other hand, if we only use maven for builds, maybe it doesn't matter.

I'll look a closer at your branch in a bit.

cheers,
Paul

[Cheong Chung Onn]

Please find my response inline

Paul Lorenz wrote:
> Hi chung-onn,
> Thanks for trying this out. I fixed the circular reference. I just
> put it back in EditorGraph, since that's the only place it was used.
>
> I hadn't thought of using symlinks. That's a neat idea. Subversion
> handles symlinks just like regular files, so no problem there.
> However, you are correct, this will not work on windows. This isn't a
> large concern for me personally, however, I don't want to discourage
> developers who work on Windows. On the other hand, if we only use
> maven for builds, maybe it doesn't matter.

I dont know how to create the symbolic link and I can't seems to get it
done using subclipse. Btw, i tried another approach, which i borrowed
the idea from you (common folder) i.e. svn:externals. The "external"
folder does not appear to follow the subfolders. Here's the svn
properties i used on sarasvati-core/src/main/java "../../../src/com
com". I belive i am missing something as i have the following errors in
my console

svn:
'/home/chungonn/development/projects/wf-java-maven/sarasvati-core/src/main/java/com'
is not under version control

Regards
chung-onn