Hello Again Wolfgang,

Please find some comments inline.

On Aug 24, 2009, at 12:22 , Schrecker, Wolfgang wrote:

Nowhere, Fotis,
because it has nothing to do with with eclipse:eclipse. It concerns Maven.
When your pom.xml is fine, eclipse:eclipse will tell eclipse so.


My pom is fine, since I can, from the command line, builld all the modules and run an equinox container. My issue is that this is by far a development set up, too long
to build and run, lack of debugging, hot code replacement and so on.

Will eclipse:eclipse the me when the pom is not fine?


Check the book 'Modular Java: Creating Flexible Applications with OSGi and Spring (Pragmatic Programmers)' Since the author is using the pax/OSGI stuff with maven, it is all in there.


Actually that is where I got most of my info :-). I didn't see anything about a development environment, most of it was ide agnostic, all on the command line. But I will take a closer look.


And it is usually good to patiently learn more about Maven ....


Patient is a virtue :-), provide by time...


Best Regards and Thank you,

Fotis


good luck
Wolfgang


-----Ursprüngliche Nachricht-----
Von: Fotis Paraskevopoulos [mailto:[email protected]]
Gesendet: Montag, 24. August 2009 11:00
An: Maven Users List
Betreff: Re: AW: Maven - Eclipse - OSGi, code, compile test cycle [Virus checked]

Hello Wolfgang,

Thank you for your reply, but where is it documented in the
eclipse:eclipse plugin that the repositories need to be
pax/OSGi?

Please correct me if I am wrong, but I have done the following.

All of the possible osgi ready jars I have gotten from the
springsource enterprise repository. Some are direct
dependencies, whilst others are transitive, like jasper-reports, needs
commons-collections and so on, all
this is fine and dandy on the command line.

The jars that are not osgi ready, I have wrapped under my project, and
I have tested their exported packages.

All of this information lives under the parent project, the effective
pom for any of the modules shows that
on the maven side everything is correct. The project builds succesfuly
which is a start :-).

Bellow I am posting the reposttory section of my pom, just in case you
can spot anything weird, which might
be disturbing the correct eclipse:eclipse functionality.

<repositories>
    <repository>
      <id>java.net.maven2</id>
      <name>Java Net Maven 2 - Repository</name>
      <url>http://download.java.net/maven/2/</url>
    </repository>
    <repository>
      <id>com.springsource.repository.bundles.release</id>
      <name>SpringSource Enterprise Bundle Repository - SpringSource
Bundle Releases</name>
      <url>http://repository.springsource.com/maven/bundles/release</
url>
    </repository>
    <repository>
      <id>com.springsource.repository.bundles.external</id>
      <name>SpringSource Enterprise Bundle Repository - External
Bundle Releases</name>
      <url>http://repository.springsource.com/maven/bundles/external</
url>
    </repository>
    <repository>
      <id>bits.netbeans.org.maven2</id>
      <name>Netbeans Maven 2 - Repository</name>
      <url>http://bits.netbeans.org/maven2</url>
    </repository>
    <repository>
      <id>repository.jboss.com.maven2</id>
      <name>JBoss Maven 2 - Repository</name>
      <url>http://repository.jboss.com/maven2</url>
    </repository>
  </repositories>

Best Regards,
Fotis



On Aug 24, 2009, at 11:47 , Schrecker, Wolfgang wrote:

Hello,
did you make sure, that in the MAVEN settings.xml or your pom.xml,
there is a correct entry for the pax/OSGI repositories ?
AFAIK, they are NOT the standard Maven repo.

Wolfgang

-----Ursprüngliche Nachricht-----
Von: Fotis Paraskevopoulos [mailto:[email protected]]
Gesendet: Montag, 24. August 2009 08:51
An: [email protected]
Betreff: Maven - Eclipse - OSGi, code, compile test cycle [Virus
checked]

Hello All,

This is my first message to the list, so I hope I am able to ask my
question correctly.

I migrated a project to OSGi using the eclipse PDE tools. This was
handy enough
because I could immediately see the errors, when making changes to the
MANIFEST.MF,
between plugins and run debug the project under the equinox framework.

I then came to the necessity of building my system, and after asking
around the concesous
was to use Maven. So after reading the Sonatype book, I set out to
mavenize my project.

The first hurdle was on how to set up the projects so that I could
keep working with Eclipse,
I read a post somewhere where  they kept saying (There is no spoon),
refering to the fact
that maven and eclipse don't know of each other's existence.

I can't get my head around on how people develop using maven for the
build and eclipse
for the coding.  I am currently using the m2eclipse plugin, and the
pax tools for my
osgi project, along with the eclipse:eclipse plugin to eclipzise my
maven projects. The problem
is that the classpath is all wrong, I have no debug capabilites, each
time I make a change to either
the code  I have to do mvn install, (which for one of the bundles,the
compile time is ridiculous)
and then run using pax-provision(off-topic but this takes at least
70 seconds) to run the
project in an equinox container. All this on the command-line, outside
of my development
environement. There must be a better way.

Let me just say, that I have tested both setups for my project, a
workspace with a flat layout for
the modules, and a workspace where there is a root project, and the
modules are
underneath, just like maven likes it. This is not a huge project, but
it is 20+ bundles, and
doing all the work of laying it out is not the easiest thing in the
world.

So hoping that some soul in the list is using eclipse with maven to
build osgi
bunldes (Not eclipse plugins), I have several questions.

eclipse:eclipse -
In the website it states that

"Linked Resources
In order for the Eclipse PDE system to build or deploy an Eclipse PDE
project, it requires that dependent jars exist somewhere within the
project itself.

By default, the eclipse:eclipse goal sets up the Eclipse classpath
such that the project depends on jars in the external local maven
repository.

When PDE mode is enabled, dependencies are configured as Eclipse
linked resources instead. Eclipse linked resources work like symbolic
links within

the Eclipse IDE. These linked resources appear in the root directory
of your PDE project, and link the jars within your repository into the
root of your project as required by Eclipse."

But this is not the case for me. "Some" of the libraries do get linked
but not all (specially those comming from the the sprinsource repo).
If this worked properly, I would at least have solved the classpath
problem.



So how do you make it work, is there any special setup needed in my
settings.xml, am I using the wrong

repositories. Does this just doesn't work?



How do you handle transitive dependencies?



Manifest:-

Using the manifest plugin, to generate the manifest with the (maven-
bundle-plugin) is ok but sometime it adds

erroneous new lines which causes PDE to cry. And of course the path to
the jars is wrong, because anything

listed under Bundle-Classpath doesn't exist in the classpath.



So to summarize, I would like if someone can help me out in wiring all
this up, I know that as per the rules of posting,

when it is urgent, it urgent only for me, but this is really urgent.



Best Regards,

Fotis

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstrasse 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax :
mailto: [email protected]
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
This e-mail is destined for the above mentioned recipient. In case you
received this e-mail by accident, we would appreciate it if you could
contact the sender and delete all copies stored on your computer.
Please be aware that the security and confidentiality of electronic
data
transmitted by e-mail is not completely guaranteed and that data may
be seen,
copied, downloaded or changed by third persons during transmission.
Atos Origin accepts no liability for the security and
confidentiality of
data and documents sent by e-mail. Please make sure that all important
messages will be confirmed in writing by means of a telefax or a
letter.
* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstrasse 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax :
mailto: [email protected]
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
This e-mail is destined for the above mentioned recipient. In case you
received this e-mail by accident, we would appreciate it if you could
contact the sender and delete all copies stored on your computer.
Please be aware that the security and confidentiality of electronic data transmitted by e-mail is not completely guaranteed and that data may be seen,
copied, downloaded or changed by third persons during transmission.
Atos Origin accepts no liability for the security and confidentiality of
data and documents sent by e-mail. Please make sure that all important
messages will be confirmed in writing by means of a telefax or a letter.
* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to