Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

For the upcoming Empire-db 2.0.5. release we plan to provide Maven support.

 

We are however still struggling to find someone with good Maven skills who is willing to help us with that task.

 

So if anyone out there is good with Maven and has the time and will to support us, we would very much appreciate to hear from you.

 

Rainer
 

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,
Hi Francis,

I am terribly sorry for not having been able to reply to your E-Mail earlier.

We have held the vote last week and I think we have got the required three votes. I am waiting for Jörg to post the result and possibly inform the Incubator PMC.
@Jörg: what is the state of the vote?

As for the empire-db-struts2: There is not a single person responsible for a certain part of the project. Just post you questions or suggestions to the dev list and I will comment on it (if no one else replies first).

Sorry again for the delay in communication. But we all have jobs and family.

Regards
Rainer


Francis De Brabandere wrote:
> 
> Any updates on me becoming a committer?
> Who is responsible for empire-db-struts2?
> 
> On Mon, Nov 17, 2008 at 10:38 AM, Francis De Brabandere
> <fr...@gmail.com> wrote:
> > Hi,
> >
> > I just read that incubating releases can not be uploaded to the
> > central maven repository, there is a separate repository available for
> > those:
> > http://www.apache.org/dev/repository-faq.html
> >
> > Further I need to know what the real dependencies are for
> > empire-db-struts2, the lib dir also contains transitive dependencies
> > (dependencies of dependencies) but I should not declare those in the
> > pom files.
> >
> > I set up a temp testing repository at maven.somatik.be
> >                <repository>
> >                  <id>maven.somatik.be</id>
> >                  <name>Somatik Repository for Maven</name>
> >                  <url>http://maven.somatik.be</url>
> >                  <layout>default</layout>
> >                </repository>
> >
> > with the following artifact available:
> > <dependency>
> >                <groupId>org.apache.empire</groupId>
> >                <artifactId>empire-db</artifactId>
> >                <version>2.0.4-incubating</version>
> >        </dependency>
> > (source and javadoc jar are not in there yet)
> >
> > Is the groupid and artifactid correct?
> >
> > Francis
> >
> >
> > On Sun, Nov 16, 2008 at 8:33 PM, Rainer Döbele <do...@esteam.de>
> wrote:
> >> Hi Francis,
> >>
> >> excellent.
> >> Hennig (our sponsor) has told me in the meatime how to get you on.
> >> We (i.e. the existing Empire-db committers) have to vote you in.
> >> Therefore we have to call for a vote and get at least three positive
> votes
> >> (which should not be a problem).
> >>
> >> Jörg, you're the voting master.
> >> Would you be so kind and call for a vote again concering accepting
> Francis
> >> as our new committer?
> >>
> >> Concering upcoming release 2.0.5.:
> >> So far, we have only a few minor bugfixes and small improvements to
> publish.
> >> But the Maven thing would be a good reason to get a new release out.
> >>
> >> However publishing releases can sometimes be tedious in the incubator.
> >> Once we all have accepted the release the Incubator PMC has to accept
> is as
> >> well.
> >>
> >> We had to fight long and hard to get the previous release accepted due
> to
> >> some legal concerns.
> >> That should be better this time around, but you never know.
> >>
> >> Rainer
> >>
> >>
> >> Francis De Brabandere wrote:
> >>>
> >>> I'll take care of the Contributor License Agreement this evening.
> >>>
> >>> > Still I plead for a smooth transition in two phases:
> >>> >
> >>> > Phase one: Take the current distribution
> >>> > (apache-empire-db-2.0.4-incubating
> >>> > and apache-empire-struts2-ext-1.0.4-incubating from
> >>> > http://www.apache.org/dist/incubator/empire-db) and restructure it
> for
> >>> > Maven
> >>> > in a way that it best possibly conforms to all Maven conventions.
> This
> >>> > would
> >>> > also include putting all required files into the maven repository.
> Next
> >>> > we
> >>> > will change our distribution scripts to build the distribution in
> that
> >>> > way
> >>> > for the 2.0.5 release.
> >>>
> >>> Uploading the current distribution to the central repo should not be a
> >>> problem. I'll make the needed pom files and stuff.
> >>> (http://maven.apache.org/guides/mini/guide-central-repository-
> upload.html)
> >>>
> >>> >
> >>> > Phase two: Once the 2.0.5. release is out and everybody had a chance
> to
> >>> > see
> >>> > the benefits, we can restructure our internal SVN structure in the
> same
> >>> > way.
> >>> >
> >>>
> >>> Is the 2.0.5 release planned for the near future?
> >>>
> >>> Regards,
> >>>
> >>> Francis
> >>>
> >>> > I hope this approach is feasible and if so I think it is sensible.
> >>> > We should possibly consider all options and call for a vote.
> >>> >
> >>> > Regards
> >>> > Rainer
> >>> >
> >>> > Francis De Brabandere wrote:
> >>> >>
> >>> >>> Personally I am open for any kind of change if I can see the
> >>> >>> advantage.
> >>> >>> For
> >>> >>> the moment however I would prefer starting with a Maven solution
> for
> >>> >>> the
> >>> >>> users of the distribution first, and maybe later on we can change
> the
> >>> >>> internal project layout too.
> >>> >>> What do you think?
> >>> >>
> >>> >> Well the problem is that just creating some pom files without
> changing
> >>> >> the project structure would complicate the maven build a lot. As
> >>> >> Martijn said, maven is all about conventions, trying to fight those
> is
> >>> >> looking for trouble. Maven has proven itself and is used by some of
> >>> >> the biggest open source java frameworks. The advantage is that when
> >>> >> you know how a maven project is structured, you feel at home in any
> >>> >> maven based project out there.
> >>> >>
> >>> >> Users using maven for their build typically don't even care how
> your
> >>> >> project is built or released. All they care about is that the files
> >>> >> are available in the central maven repository (or some other public
> >>> >> repo) and that all needed dependencies are configured correctly.
> For
> >>> >> them the distribution you are talking about is not needed: the
> source,
> >>> >> binaries and javadoc will be fetched during the initial build and
> set
> >>> >> up in their ide.  The first thing I do when some of my projects
> need
> >>> >> and extra dependency is looking it up on
> http://www.mvnrepository.com/
> >>> >> (I even use their RSS feed to keep myself up to date on the new
> >>> >> releases for java related frameworks)
> >>> >>
> >>> >> Maven is able to perform the task of both build files you described.
> >>> >> Distribution files can be built using the assembly plugin (ex
> >>> >> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-
> all.xml).
> >>> >>
> >>> >> Francis
> >>> >>
> >>
> >
> >
> >
> > --
> > http://www.somatik.be
> > Microsoft gives you windows, Linux gives you the whole house.
> >
> 
> 
> 
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.

Re: Empire-db and Empire-Struts2-ext distribution with Maven support

[Martijn Dashorst <ma...@gmail.com>]

You fail to see what Maven is: it is not a build tool, it is a
distribution mechanism. You don't typically distribute a zip file with
a maven build inside, you distribute your project through maven. You
distribute your empire-db jars through the maven repository, you
distribute your source through maven and you distribute your javadoc
through maven, and you build a source/binary distribution for those
that don't use maven, with maven.

A maven pom inside the distribution is only beneficial for those that
want to build themselves from source, but the vast majority just wants
to get started with the product and not go on a jar hunt, or have to
manually install jars into their own maven repository.

To put things in perspective: with Wicket the vast majority of our
users obtain Wicket through maven. I might even say 70%-80%.

Therefore I agree with Francis that the main build should be based on
maven, not the distribution.

Martijn

On Wed, Dec 3, 2008 at 10:24 AM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> yes, when I mentioned the two steps my intention was to first mavenize the distribution and later the svn repository.
>
> What I still don't see is why it would be easier to make the distribution if we convert the svn repo first. Also I don't see why any of your work would ever be lost. The releas scripts would be changed and every new release will be built according to this (I could do that).
>
> For me, the distribution does not have to contain any kind of reference to the svn repository. The distribution has three main purposes:
>
> 1. Supply the binaries and the source for debugging
> 2. Provide example application that show how to work with the distribution
> 3. Build the binaries from the source.
>
> For Point 1 and 2 I don't think we need a svn history. Even for Point 3 I personally don't feel the need for a history. The distribution is for end-users and not really for people who want to work on the project itself.
>
> Also we need to address the fact, that the way the projects are set up in Eclipse differs between internal development and distribution. For example: The DBSample contains all required jars in the classpath whereas in our internal development it contains a reference to the Empire-db Eclipse project and other sub-projects.
>
> Nobody wants you to put in work that will later be lost - but as I said I don't see why that would be. It's certainly a lot more work and stress to convert the whole svn repo now in one go.
>
> I just feel that if we start moving around files in svn now, we might face serious problems with working on the project - which we as Maven novices could find hard to solve ourselves. But if we have a mavenized distribution first, we could all get familiar with it and then go for the big bang later.
>
> This is my personal point of view. But we're a community and everyone should give their opinion.
>
> Before we end up having an endless discussion however, we should start reaching a agreement on what to do. Now it's all down to the point whether to mavenize the distribution only for a start or go for the big bang and modify the svn.
> I would still prefer modifying the distribution first and do the rest later.
> Again: What exactly would be the disadvantage of that why would we find it harder to modify the svn later?
>
> Rainer
>
>
> Francis De Brabandere wrote:
>>
>> Jürg, Rainer,
>>
>> As Jürg suggested, big bang is the easiest way to get everything ready
>> for maven. If I understand correctly you suggest I start with a svn
>> trunk checkout (or the distribution), start moving stuff around and
>> mavenize it until is possible to build the distribution zip. All svn
>> history will be lost if you just check that version in... Won't that
>> be a problem? And you'll have to stop coding during that time?
>>
>> Rainer, I still don't see why you want the distribution mavenized and
>> not the code repository?
>>
>> I really think this should be done by somebody inside the project with
>> access to subversion. It is going to be a lot more work if I do this
>> locally and afterwards you guys try to merge the whole thing...
>>
>> Am I correct to understand that the team is afraid of messing up the
>> ant build by moving files in svn? Last time I merged a project to
>> maven I started by moving files around (in small steps) towards the
>> maven layout, and while doing that I updated the build file(s). When
>> everything was correctly in place I then just added the pom files and
>> configured the maven build. At that point we had 2 operational build
>> systems. Maybe that's an easier way for you guys to move to maven?
>>
>> It's just that I don't want to put time and effort in all the
>> migration work to see it being lost afterwards. Have you asked other
>> maven users (Martijn?) what they think about all this?
>>
>> Francis
>>
>> On Mon, Dec 1, 2008 at 6:58 PM, Rainer Döbele <do...@esteam.de> wrote:
>> > Hi Francis,
>> >
>> > Sorry for not being able to reply earlier.
>> > Please also apologize if I am unable to understand you or express myself.
>> >
>> > If I understand it right, the first thing to do is to create artefacts
>> for both empire-db-2.0.4.jar and empire-struts3-ext-1.0.4.jar and put them
>> in a Maven repository so that people can use it in their projects. This
>> would be the first thing to do, right?
>> >
>> > Next, we need to supply a file for download to the user (zip or tar.gz).
>> This is what I call 'the distribution'. It should contain the following:
>> > - Apache License files, the readme and the changelog
>> > - a lib directory containing the distribution jar's (e.g. empire-db-
>> 2.0.4.jar) - with or without dependencies.
>> > - a src folder containing the project source, the examples, and the
>> necessary pom.xml files required to build the Eclipse projects for both
>> building the empire jars and the example applications.
>> > For every new Release there will be one distribution file for each of
>> the two projects.
>> >
>> > My idea is, that you restructure the current distribution so that it is
>> structured similar to e.g. the Maven distribution
>> (http://apache.imsam.info/wicket/1.4-rc1/apache-wicket-1.4-rc1.zip ) and
>> send the whole thing back to me. I will then make sure, that for our next
>> release the distribution will look like this.
>> >
>> > I understand you, you would rather recommend leaving the current
>> distribution as it is and just add the pom.xml files for building the
>> project and for building the examples.
>> >
>> > So the only thing we're still not clear about, is what the distribution
>> file should look like.
>> >
>> > Do you agree with that?
>> >
>> > Regards
>> > Rainer
>> >
>> > Francis De Brabandere wrote:
>> >> Betreff: Re: Empire-db and Empire-Struts2-ext distribution with Maven
>> >> support
>> >>
>> >> Rainer,
>> >>
>> >> I'm still not sure we are talking about the same things as you keep
>> >> mentioning the 'distribution'... In the maven world your distribution
>> >> is uploading artifacts to a maven repository. So for maven users you
>> >> want to set up that repository. There is no need to change anything in
>> >> the current distribution layout/files. I would only create a pom file
>> >> for each artifact and upload that that together with the jar, src jar
>> >> and doc jar to a repository. (this will however take time on every
>> >> release and we want to keep this period short and go to step 2 [full
>> >> maven build] as fast as possible)
>> >>
>> >> The only remaining thing I need here is the *direct* dependencies for
>> >> the struts2 ext.
>> >>
>> >> [step 2]
>> >> Now if we talk about the source repo (subversion) and you want to
>> >> migrate the project to maven the repository should be restructured
>> >> (like wicket). As an option you may want to keep the ant build
>> >> available (update the build.xml). Once this is taken care of we can
>> >> define the "distribution" in the maven build and from then on maven
>> >> will generate the distribution file (that can be used by non-maven
>> >> users).
>> >> see this file for an example distribution configuration:
>> >> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml
>> >>
>> >> I hope I made myself clear this time :-)
>> >>
>> >> Regards,
>> >>
>> >> Francis
>> >>
>> >>
>> >> On Fri, Nov 28, 2008 at 10:52 PM, Rainer Döbele <do...@esteam.de>
>> wrote:
>> >> > Hi Francis,
>> >> >
>> >> > do whatever needs to be done for step 1.
>> >> >
>> >> > As fas as the distribution layout is concerned I was having a look at
>> >> other Apache projects and how they do it.
>> >> > Take e.g. Apache Wicket
>> >> (http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1) or Apache CXF
>> >> (http://cxf.apache.org/download.html)
>> >> >
>> >> > We should structure our distribution in a similar fashion so that it
>> >> best fits Maven.
>> >> > But if you think that we can leave our layout and just add the pom-
>> files
>> >> that's fine by me.
>> >> >
>> >> > I know that the dependencies are not supplied with the Apache Wicket
>> and
>> >> Apache CXF distribtions but are fechted by Maven.
>> >> > The question is, can we still provide the jars in order to allow a
>> >> simple ant build and leave Maven as an option?
>> >> >
>> >> > Whatever you do, it should be a good solutions that give the user an
>> >> adavantage over the existing approach.
>> >> > Let me know if I can be of any help.
>> >> >
>> >> > Regards
>> >> > Rainer
>> >> >
>> >> > P.S. Are you working a lot with databases and have you used Empire-db
>> so
>> >> far?
>> >> >
>> >> >
>> >> > Francis De Brabandere wrote:
>> >> >> Re: Information about the empire-struts2-ext distribution
>> >> >>
>> >> >> Rainer,
>> >> >>
>> >> >> Thanks for the info but I don't think we are talking about the same
>> >> thing.
>> >> >> Let's think about what a maven user would like from the empire-db
>> >> project.
>> >> >>
>> >> >> As a maven user you declare dependencies to other artifacts (jar's)
>> to
>> >> >> have them fetched on build/eclipse project setup time. So what you
>> >> >> gain is not having to download a distribution or whatever is used to
>> >> >> build the library you want to use. All you do is define where the
>> >> >> dependencies' artifacts are located (if not in the central repo) and
>> >> >> which they are. What you are talking about is that the user can
>> >> >> download the "distribution" and build it including samples using
>> >> >> maven. I don't see any value in that, I want to *build my* project
>> >> >> using maven and *use your* library without too much
>> >> >> configuration/setup.
>> >> >>
>> >> >> So what are the steps to provide empire as dependency in maven:
>> >> >>
>> >> >> - Create main jar, source jar, and javadoc jar
>> >> >> - Define pom for empire (including definitions of the dependencies)
>> >> >> - upload everything to a (temporary) repo that the users can define
>> in
>> >> >> their project setup.
>> >> >>
>> >> >> And these steps should be performed for the struts 2 ext as well.
>> >> >>
>> >> >> Now for dependencies definitions, maven has a system of transitive
>> >> >> dependencies, dependencies of dependencies. For example if we take
>> the
>> >> >> pom for struts2-core:
>> >> >> http://www.mvnrepository.com/artifact/org.apache.struts/struts2-
>> >> core/2.1.2
>> >> >> you can see that this artifact depends on a lot of other artifacts.
>> >> >> That was why I was asking you to let me know what the *real*
>> >> >> dependencies are for empire struts2. There is no direct dependency
>> for
>> >> >> ognl I suppose, this is a struts2 dependency, not a empire struts2
>> ext
>> >> >> one.
>> >> >>
>> >> >> The point is that preparing all the above is easily done when empire
>> >> >> is using using maven for its own build. And that would be step 2.
>> Once
>> >> >> the maven repo is set up we could also transform the DBWebSample to
>> a
>> >> >> maven build (as step 1.5) so that the example can be run using maven.
>> >> >>
>> >> >> Summary: set up a (temp) maven repo + transform sample to maven as
>> >> >> test, or move the whole empire build to maven (big bang)
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> Francis
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://www.somatik.be
>> >> Microsoft gives you windows, Linux gives you the whole house.
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

Re: Empire-db and Empire-Struts2-ext distribution with Maven support

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

yes, when I mentioned the two steps my intention was to first mavenize the distribution and later the svn repository.

What I still don't see is why it would be easier to make the distribution if we convert the svn repo first. Also I don't see why any of your work would ever be lost. The releas scripts would be changed and every new release will be built according to this (I could do that).

For me, the distribution does not have to contain any kind of reference to the svn repository. The distribution has three main purposes:

1. Supply the binaries and the source for debugging
2. Provide example application that show how to work with the distribution
3. Build the binaries from the source.

For Point 1 and 2 I don't think we need a svn history. Even for Point 3 I personally don't feel the need for a history. The distribution is for end-users and not really for people who want to work on the project itself.

Also we need to address the fact, that the way the projects are set up in Eclipse differs between internal development and distribution. For example: The DBSample contains all required jars in the classpath whereas in our internal development it contains a reference to the Empire-db Eclipse project and other sub-projects.

Nobody wants you to put in work that will later be lost - but as I said I don't see why that would be. It's certainly a lot more work and stress to convert the whole svn repo now in one go.

I just feel that if we start moving around files in svn now, we might face serious problems with working on the project - which we as Maven novices could find hard to solve ourselves. But if we have a mavenized distribution first, we could all get familiar with it and then go for the big bang later.

This is my personal point of view. But we're a community and everyone should give their opinion.

Before we end up having an endless discussion however, we should start reaching a agreement on what to do. Now it's all down to the point whether to mavenize the distribution only for a start or go for the big bang and modify the svn. 
I would still prefer modifying the distribution first and do the rest later.
Again: What exactly would be the disadvantage of that why would we find it harder to modify the svn later?

Rainer


Francis De Brabandere wrote:
> 
> Jürg, Rainer,
> 
> As Jürg suggested, big bang is the easiest way to get everything ready
> for maven. If I understand correctly you suggest I start with a svn
> trunk checkout (or the distribution), start moving stuff around and
> mavenize it until is possible to build the distribution zip. All svn
> history will be lost if you just check that version in... Won't that
> be a problem? And you'll have to stop coding during that time?
> 
> Rainer, I still don't see why you want the distribution mavenized and
> not the code repository?
> 
> I really think this should be done by somebody inside the project with
> access to subversion. It is going to be a lot more work if I do this
> locally and afterwards you guys try to merge the whole thing...
> 
> Am I correct to understand that the team is afraid of messing up the
> ant build by moving files in svn? Last time I merged a project to
> maven I started by moving files around (in small steps) towards the
> maven layout, and while doing that I updated the build file(s). When
> everything was correctly in place I then just added the pom files and
> configured the maven build. At that point we had 2 operational build
> systems. Maybe that's an easier way for you guys to move to maven?
> 
> It's just that I don't want to put time and effort in all the
> migration work to see it being lost afterwards. Have you asked other
> maven users (Martijn?) what they think about all this?
> 
> Francis
> 
> On Mon, Dec 1, 2008 at 6:58 PM, Rainer Döbele <do...@esteam.de> wrote:
> > Hi Francis,
> >
> > Sorry for not being able to reply earlier.
> > Please also apologize if I am unable to understand you or express myself.
> >
> > If I understand it right, the first thing to do is to create artefacts
> for both empire-db-2.0.4.jar and empire-struts3-ext-1.0.4.jar and put them
> in a Maven repository so that people can use it in their projects. This
> would be the first thing to do, right?
> >
> > Next, we need to supply a file for download to the user (zip or tar.gz).
> This is what I call 'the distribution'. It should contain the following:
> > - Apache License files, the readme and the changelog
> > - a lib directory containing the distribution jar's (e.g. empire-db-
> 2.0.4.jar) - with or without dependencies.
> > - a src folder containing the project source, the examples, and the
> necessary pom.xml files required to build the Eclipse projects for both
> building the empire jars and the example applications.
> > For every new Release there will be one distribution file for each of
> the two projects.
> >
> > My idea is, that you restructure the current distribution so that it is
> structured similar to e.g. the Maven distribution
> (http://apache.imsam.info/wicket/1.4-rc1/apache-wicket-1.4-rc1.zip ) and
> send the whole thing back to me. I will then make sure, that for our next
> release the distribution will look like this.
> >
> > I understand you, you would rather recommend leaving the current
> distribution as it is and just add the pom.xml files for building the
> project and for building the examples.
> >
> > So the only thing we're still not clear about, is what the distribution
> file should look like.
> >
> > Do you agree with that?
> >
> > Regards
> > Rainer
> >
> > Francis De Brabandere wrote:
> >> Betreff: Re: Empire-db and Empire-Struts2-ext distribution with Maven
> >> support
> >>
> >> Rainer,
> >>
> >> I'm still not sure we are talking about the same things as you keep
> >> mentioning the 'distribution'... In the maven world your distribution
> >> is uploading artifacts to a maven repository. So for maven users you
> >> want to set up that repository. There is no need to change anything in
> >> the current distribution layout/files. I would only create a pom file
> >> for each artifact and upload that that together with the jar, src jar
> >> and doc jar to a repository. (this will however take time on every
> >> release and we want to keep this period short and go to step 2 [full
> >> maven build] as fast as possible)
> >>
> >> The only remaining thing I need here is the *direct* dependencies for
> >> the struts2 ext.
> >>
> >> [step 2]
> >> Now if we talk about the source repo (subversion) and you want to
> >> migrate the project to maven the repository should be restructured
> >> (like wicket). As an option you may want to keep the ant build
> >> available (update the build.xml). Once this is taken care of we can
> >> define the "distribution" in the maven build and from then on maven
> >> will generate the distribution file (that can be used by non-maven
> >> users).
> >> see this file for an example distribution configuration:
> >> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml
> >>
> >> I hope I made myself clear this time :-)
> >>
> >> Regards,
> >>
> >> Francis
> >>
> >>
> >> On Fri, Nov 28, 2008 at 10:52 PM, Rainer Döbele <do...@esteam.de>
> wrote:
> >> > Hi Francis,
> >> >
> >> > do whatever needs to be done for step 1.
> >> >
> >> > As fas as the distribution layout is concerned I was having a look at
> >> other Apache projects and how they do it.
> >> > Take e.g. Apache Wicket
> >> (http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1) or Apache CXF
> >> (http://cxf.apache.org/download.html)
> >> >
> >> > We should structure our distribution in a similar fashion so that it
> >> best fits Maven.
> >> > But if you think that we can leave our layout and just add the pom-
> files
> >> that's fine by me.
> >> >
> >> > I know that the dependencies are not supplied with the Apache Wicket
> and
> >> Apache CXF distribtions but are fechted by Maven.
> >> > The question is, can we still provide the jars in order to allow a
> >> simple ant build and leave Maven as an option?
> >> >
> >> > Whatever you do, it should be a good solutions that give the user an
> >> adavantage over the existing approach.
> >> > Let me know if I can be of any help.
> >> >
> >> > Regards
> >> > Rainer
> >> >
> >> > P.S. Are you working a lot with databases and have you used Empire-db
> so
> >> far?
> >> >
> >> >
> >> > Francis De Brabandere wrote:
> >> >> Re: Information about the empire-struts2-ext distribution
> >> >>
> >> >> Rainer,
> >> >>
> >> >> Thanks for the info but I don't think we are talking about the same
> >> thing.
> >> >> Let's think about what a maven user would like from the empire-db
> >> project.
> >> >>
> >> >> As a maven user you declare dependencies to other artifacts (jar's)
> to
> >> >> have them fetched on build/eclipse project setup time. So what you
> >> >> gain is not having to download a distribution or whatever is used to
> >> >> build the library you want to use. All you do is define where the
> >> >> dependencies' artifacts are located (if not in the central repo) and
> >> >> which they are. What you are talking about is that the user can
> >> >> download the "distribution" and build it including samples using
> >> >> maven. I don't see any value in that, I want to *build my* project
> >> >> using maven and *use your* library without too much
> >> >> configuration/setup.
> >> >>
> >> >> So what are the steps to provide empire as dependency in maven:
> >> >>
> >> >> - Create main jar, source jar, and javadoc jar
> >> >> - Define pom for empire (including definitions of the dependencies)
> >> >> - upload everything to a (temporary) repo that the users can define
> in
> >> >> their project setup.
> >> >>
> >> >> And these steps should be performed for the struts 2 ext as well.
> >> >>
> >> >> Now for dependencies definitions, maven has a system of transitive
> >> >> dependencies, dependencies of dependencies. For example if we take
> the
> >> >> pom for struts2-core:
> >> >> http://www.mvnrepository.com/artifact/org.apache.struts/struts2-
> >> core/2.1.2
> >> >> you can see that this artifact depends on a lot of other artifacts.
> >> >> That was why I was asking you to let me know what the *real*
> >> >> dependencies are for empire struts2. There is no direct dependency
> for
> >> >> ognl I suppose, this is a struts2 dependency, not a empire struts2
> ext
> >> >> one.
> >> >>
> >> >> The point is that preparing all the above is easily done when empire
> >> >> is using using maven for its own build. And that would be step 2.
> Once
> >> >> the maven repo is set up we could also transform the DBWebSample to
> a
> >> >> maven build (as step 1.5) so that the example can be run using maven.
> >> >>
> >> >> Summary: set up a (temp) maven repo + transform sample to maven as
> >> >> test, or move the whole empire build to maven (big bang)
> >> >>
> >> >> Regards,
> >> >>
> >> >> Francis
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> http://www.somatik.be
> >> Microsoft gives you windows, Linux gives you the whole house.
> >
> 
> 
> 
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.

Re: Empire-db and Empire-Struts2-ext distribution with Maven support

[Francis De Brabandere <fr...@gmail.com>]

Jürg, Rainer,

As Jürg suggested, big bang is the easiest way to get everything ready
for maven. If I understand correctly you suggest I start with a svn
trunk checkout (or the distribution), start moving stuff around and
mavenize it until is possible to build the distribution zip. All svn
history will be lost if you just check that version in... Won't that
be a problem? And you'll have to stop coding during that time?

Rainer, I still don't see why you want the distribution mavenized and
not the code repository?

I really think this should be done by somebody inside the project with
access to subversion. It is going to be a lot more work if I do this
locally and afterwards you guys try to merge the whole thing...

Am I correct to understand that the team is afraid of messing up the
ant build by moving files in svn? Last time I merged a project to
maven I started by moving files around (in small steps) towards the
maven layout, and while doing that I updated the build file(s). When
everything was correctly in place I then just added the pom files and
configured the maven build. At that point we had 2 operational build
systems. Maybe that's an easier way for you guys to move to maven?

It's just that I don't want to put time and effort in all the
migration work to see it being lost afterwards. Have you asked other
maven users (Martijn?) what they think about all this?

Francis

On Mon, Dec 1, 2008 at 6:58 PM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> Sorry for not being able to reply earlier.
> Please also apologize if I am unable to understand you or express myself.
>
> If I understand it right, the first thing to do is to create artefacts for both empire-db-2.0.4.jar and empire-struts3-ext-1.0.4.jar and put them in a Maven repository so that people can use it in their projects. This would be the first thing to do, right?
>
> Next, we need to supply a file for download to the user (zip or tar.gz). This is what I call 'the distribution'. It should contain the following:
> - Apache License files, the readme and the changelog
> - a lib directory containing the distribution jar's (e.g. empire-db-2.0.4.jar) - with or without dependencies.
> - a src folder containing the project source, the examples, and the necessary pom.xml files required to build the Eclipse projects for both building the empire jars and the example applications.
> For every new Release there will be one distribution file for each of the two projects.
>
> My idea is, that you restructure the current distribution so that it is structured similar to e.g. the Maven distribution (http://apache.imsam.info/wicket/1.4-rc1/apache-wicket-1.4-rc1.zip ) and send the whole thing back to me. I will then make sure, that for our next release the distribution will look like this.
>
> I understand you, you would rather recommend leaving the current distribution as it is and just add the pom.xml files for building the project and for building the examples.
>
> So the only thing we're still not clear about, is what the distribution file should look like.
>
> Do you agree with that?
>
> Regards
> Rainer
>
> Francis De Brabandere wrote:
>> Betreff: Re: Empire-db and Empire-Struts2-ext distribution with Maven
>> support
>>
>> Rainer,
>>
>> I'm still not sure we are talking about the same things as you keep
>> mentioning the 'distribution'... In the maven world your distribution
>> is uploading artifacts to a maven repository. So for maven users you
>> want to set up that repository. There is no need to change anything in
>> the current distribution layout/files. I would only create a pom file
>> for each artifact and upload that that together with the jar, src jar
>> and doc jar to a repository. (this will however take time on every
>> release and we want to keep this period short and go to step 2 [full
>> maven build] as fast as possible)
>>
>> The only remaining thing I need here is the *direct* dependencies for
>> the struts2 ext.
>>
>> [step 2]
>> Now if we talk about the source repo (subversion) and you want to
>> migrate the project to maven the repository should be restructured
>> (like wicket). As an option you may want to keep the ant build
>> available (update the build.xml). Once this is taken care of we can
>> define the "distribution" in the maven build and from then on maven
>> will generate the distribution file (that can be used by non-maven
>> users).
>> see this file for an example distribution configuration:
>> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml
>>
>> I hope I made myself clear this time :-)
>>
>> Regards,
>>
>> Francis
>>
>>
>> On Fri, Nov 28, 2008 at 10:52 PM, Rainer Döbele <do...@esteam.de> wrote:
>> > Hi Francis,
>> >
>> > do whatever needs to be done for step 1.
>> >
>> > As fas as the distribution layout is concerned I was having a look at
>> other Apache projects and how they do it.
>> > Take e.g. Apache Wicket
>> (http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1) or Apache CXF
>> (http://cxf.apache.org/download.html)
>> >
>> > We should structure our distribution in a similar fashion so that it
>> best fits Maven.
>> > But if you think that we can leave our layout and just add the pom-files
>> that's fine by me.
>> >
>> > I know that the dependencies are not supplied with the Apache Wicket and
>> Apache CXF distribtions but are fechted by Maven.
>> > The question is, can we still provide the jars in order to allow a
>> simple ant build and leave Maven as an option?
>> >
>> > Whatever you do, it should be a good solutions that give the user an
>> adavantage over the existing approach.
>> > Let me know if I can be of any help.
>> >
>> > Regards
>> > Rainer
>> >
>> > P.S. Are you working a lot with databases and have you used Empire-db so
>> far?
>> >
>> >
>> > Francis De Brabandere wrote:
>> >> Re: Information about the empire-struts2-ext distribution
>> >>
>> >> Rainer,
>> >>
>> >> Thanks for the info but I don't think we are talking about the same
>> thing.
>> >> Let's think about what a maven user would like from the empire-db
>> project.
>> >>
>> >> As a maven user you declare dependencies to other artifacts (jar's) to
>> >> have them fetched on build/eclipse project setup time. So what you
>> >> gain is not having to download a distribution or whatever is used to
>> >> build the library you want to use. All you do is define where the
>> >> dependencies' artifacts are located (if not in the central repo) and
>> >> which they are. What you are talking about is that the user can
>> >> download the "distribution" and build it including samples using
>> >> maven. I don't see any value in that, I want to *build my* project
>> >> using maven and *use your* library without too much
>> >> configuration/setup.
>> >>
>> >> So what are the steps to provide empire as dependency in maven:
>> >>
>> >> - Create main jar, source jar, and javadoc jar
>> >> - Define pom for empire (including definitions of the dependencies)
>> >> - upload everything to a (temporary) repo that the users can define in
>> >> their project setup.
>> >>
>> >> And these steps should be performed for the struts 2 ext as well.
>> >>
>> >> Now for dependencies definitions, maven has a system of transitive
>> >> dependencies, dependencies of dependencies. For example if we take the
>> >> pom for struts2-core:
>> >> http://www.mvnrepository.com/artifact/org.apache.struts/struts2-
>> core/2.1.2
>> >> you can see that this artifact depends on a lot of other artifacts.
>> >> That was why I was asking you to let me know what the *real*
>> >> dependencies are for empire struts2. There is no direct dependency for
>> >> ognl I suppose, this is a struts2 dependency, not a empire struts2 ext
>> >> one.
>> >>
>> >> The point is that preparing all the above is easily done when empire
>> >> is using using maven for its own build. And that would be step 2. Once
>> >> the maven repo is set up we could also transform the DBWebSample to a
>> >> maven build (as step 1.5) so that the example can be run using maven.
>> >>
>> >> Summary: set up a (temp) maven repo + transform sample to maven as
>> >> test, or move the whole empire build to maven (big bang)
>> >>
>> >> Regards,
>> >>
>> >> Francis
>> >
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

AW: Empire-db and Empire-Struts2-ext distribution with Maven support

[Jörg Reiher <re...@esteam.de>]

Hi Francis,
If you have the time, then I'd prefer the "Big Bang". 

In addition to the already mentioned advantages of Maven (no dependencies in the svn, easier access for Maven users) this would also ease the pain of packaging a new release for Non-Maven-users, cause Maven can generate the tar.gz/zip and all the md5/sha/asc files automatically.
Till now I couldn't find a way to create all this without jumping through some console scripts.

So I'd propose that you provide a zip file with the "mavenized" structure that we can put in the empire-db svn.

If this is too much of a hazzle for now, then step 1 (providing Maven dependencies for empire-db / empire-struts-ext) + 1.5 (adapt only WebSample to Maven style and use the Maven dependencies of step 1) would be an option.

So far,
Greetings
Jörg


> -----Ursprüngliche Nachricht-----
> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
> Gesendet: Samstag, 29. November 2008 11:55
> An: empire-db-dev@incubator.apache.org
> Betreff: Re: Empire-db and Empire-Struts2-ext distribution with Maven
> support
> 
> Rainer,
> 
> I'm still not sure we are talking about the same things as you keep
> mentioning the 'distribution'... In the maven world your distribution
> is uploading artifacts to a maven repository. So for maven users you
> want to set up that repository. There is no need to change anything in
> the current distribution layout/files. I would only create a pom file
> for each artifact and upload that that together with the jar, src jar
> and doc jar to a repository. (this will however take time on every
> release and we want to keep this period short and go to step 2 [full
> maven build] as fast as possible)
> 
> The only remaining thing I need here is the *direct* dependencies for
> the struts2 ext.
> 
> [step 2]
> Now if we talk about the source repo (subversion) and you want to
> migrate the project to maven the repository should be restructured
> (like wicket). As an option you may want to keep the ant build
> available (update the build.xml). Once this is taken care of we can
> define the "distribution" in the maven build and from then on maven
> will generate the distribution file (that can be used by non-maven
> users).
> see this file for an example distribution configuration:
> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml
> 
> I hope I made myself clear this time :-)
> 
> Regards,
> 
> Francis
> 
> 
> On Fri, Nov 28, 2008 at 10:52 PM, Rainer Döbele <do...@esteam.de>
> wrote:
> > Hi Francis,
> >
> > do whatever needs to be done for step 1.
> >
> > As fas as the distribution layout is concerned I was having a look at
> other Apache projects and how they do it.
> > Take e.g. Apache Wicket
> (http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1) or Apache CXF
> (http://cxf.apache.org/download.html)
> >
> > We should structure our distribution in a similar fashion so that it
> best fits Maven.
> > But if you think that we can leave our layout and just add the pom-
> files that's fine by me.
> >
> > I know that the dependencies are not supplied with the Apache Wicket
> and Apache CXF distribtions but are fechted by Maven.
> > The question is, can we still provide the jars in order to allow a
> simple ant build and leave Maven as an option?
> >
> > Whatever you do, it should be a good solutions that give the user an
> adavantage over the existing approach.
> > Let me know if I can be of any help.
> >
> > Regards
> > Rainer
> >
> > P.S. Are you working a lot with databases and have you used Empire-db
> so far?
> >
> >
> > Francis De Brabandere wrote:
> >> Re: Information about the empire-struts2-ext distribution
> >>
> >> Rainer,
> >>
> >> Thanks for the info but I don't think we are talking about the same
> thing.
> >> Let's think about what a maven user would like from the empire-db
> project.
> >>
> >> As a maven user you declare dependencies to other artifacts (jar's)
> to
> >> have them fetched on build/eclipse project setup time. So what you
> >> gain is not having to download a distribution or whatever is used to
> >> build the library you want to use. All you do is define where the
> >> dependencies' artifacts are located (if not in the central repo) and
> >> which they are. What you are talking about is that the user can
> >> download the "distribution" and build it including samples using
> >> maven. I don't see any value in that, I want to *build my* project
> >> using maven and *use your* library without too much
> >> configuration/setup.
> >>
> >> So what are the steps to provide empire as dependency in maven:
> >>
> >> - Create main jar, source jar, and javadoc jar
> >> - Define pom for empire (including definitions of the dependencies)
> >> - upload everything to a (temporary) repo that the users can define
> in
> >> their project setup.
> >>
> >> And these steps should be performed for the struts 2 ext as well.
> >>
> >> Now for dependencies definitions, maven has a system of transitive
> >> dependencies, dependencies of dependencies. For example if we take
> the
> >> pom for struts2-core:
> >> http://www.mvnrepository.com/artifact/org.apache.struts/struts2-
> core/2.1.2
> >> you can see that this artifact depends on a lot of other artifacts.
> >> That was why I was asking you to let me know what the *real*
> >> dependencies are for empire struts2. There is no direct dependency
> for
> >> ognl I suppose, this is a struts2 dependency, not a empire struts2
> ext
> >> one.
> >>
> >> The point is that preparing all the above is easily done when empire
> >> is using using maven for its own build. And that would be step 2.
> Once
> >> the maven repo is set up we could also transform the DBWebSample to
> a
> >> maven build (as step 1.5) so that the example can be run using
> maven.
> >>
> >> Summary: set up a (temp) maven repo + transform sample to maven as
> >> test, or move the whole empire build to maven (big bang)
> >>
> >> Regards,
> >>
> >> Francis
> >
> >
> 
> 
> 
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.

Re: Empire-db and Empire-Struts2-ext distribution with Maven support

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

Sorry for not being able to reply earlier.
Please also apologize if I am unable to understand you or express myself.

If I understand it right, the first thing to do is to create artefacts for both empire-db-2.0.4.jar and empire-struts3-ext-1.0.4.jar and put them in a Maven repository so that people can use it in their projects. This would be the first thing to do, right?

Next, we need to supply a file for download to the user (zip or tar.gz). This is what I call 'the distribution'. It should contain the following:
- Apache License files, the readme and the changelog
- a lib directory containing the distribution jar's (e.g. empire-db-2.0.4.jar) - with or without dependencies.
- a src folder containing the project source, the examples, and the necessary pom.xml files required to build the Eclipse projects for both building the empire jars and the example applications.
For every new Release there will be one distribution file for each of the two projects.

My idea is, that you restructure the current distribution so that it is structured similar to e.g. the Maven distribution (http://apache.imsam.info/wicket/1.4-rc1/apache-wicket-1.4-rc1.zip ) and send the whole thing back to me. I will then make sure, that for our next release the distribution will look like this.

I understand you, you would rather recommend leaving the current distribution as it is and just add the pom.xml files for building the project and for building the examples.

So the only thing we're still not clear about, is what the distribution file should look like.

Do you agree with that?

Regards
Rainer

Francis De Brabandere wrote:
> Betreff: Re: Empire-db and Empire-Struts2-ext distribution with Maven
> support
> 
> Rainer,
> 
> I'm still not sure we are talking about the same things as you keep
> mentioning the 'distribution'... In the maven world your distribution
> is uploading artifacts to a maven repository. So for maven users you
> want to set up that repository. There is no need to change anything in
> the current distribution layout/files. I would only create a pom file
> for each artifact and upload that that together with the jar, src jar
> and doc jar to a repository. (this will however take time on every
> release and we want to keep this period short and go to step 2 [full
> maven build] as fast as possible)
> 
> The only remaining thing I need here is the *direct* dependencies for
> the struts2 ext.
> 
> [step 2]
> Now if we talk about the source repo (subversion) and you want to
> migrate the project to maven the repository should be restructured
> (like wicket). As an option you may want to keep the ant build
> available (update the build.xml). Once this is taken care of we can
> define the "distribution" in the maven build and from then on maven
> will generate the distribution file (that can be used by non-maven
> users).
> see this file for an example distribution configuration:
> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml
> 
> I hope I made myself clear this time :-)
> 
> Regards,
> 
> Francis
> 
> 
> On Fri, Nov 28, 2008 at 10:52 PM, Rainer Döbele <do...@esteam.de> wrote:
> > Hi Francis,
> >
> > do whatever needs to be done for step 1.
> >
> > As fas as the distribution layout is concerned I was having a look at
> other Apache projects and how they do it.
> > Take e.g. Apache Wicket
> (http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1) or Apache CXF
> (http://cxf.apache.org/download.html)
> >
> > We should structure our distribution in a similar fashion so that it
> best fits Maven.
> > But if you think that we can leave our layout and just add the pom-files
> that's fine by me.
> >
> > I know that the dependencies are not supplied with the Apache Wicket and
> Apache CXF distribtions but are fechted by Maven.
> > The question is, can we still provide the jars in order to allow a
> simple ant build and leave Maven as an option?
> >
> > Whatever you do, it should be a good solutions that give the user an
> adavantage over the existing approach.
> > Let me know if I can be of any help.
> >
> > Regards
> > Rainer
> >
> > P.S. Are you working a lot with databases and have you used Empire-db so
> far?
> >
> >
> > Francis De Brabandere wrote:
> >> Re: Information about the empire-struts2-ext distribution
> >>
> >> Rainer,
> >>
> >> Thanks for the info but I don't think we are talking about the same
> thing.
> >> Let's think about what a maven user would like from the empire-db
> project.
> >>
> >> As a maven user you declare dependencies to other artifacts (jar's) to
> >> have them fetched on build/eclipse project setup time. So what you
> >> gain is not having to download a distribution or whatever is used to
> >> build the library you want to use. All you do is define where the
> >> dependencies' artifacts are located (if not in the central repo) and
> >> which they are. What you are talking about is that the user can
> >> download the "distribution" and build it including samples using
> >> maven. I don't see any value in that, I want to *build my* project
> >> using maven and *use your* library without too much
> >> configuration/setup.
> >>
> >> So what are the steps to provide empire as dependency in maven:
> >>
> >> - Create main jar, source jar, and javadoc jar
> >> - Define pom for empire (including definitions of the dependencies)
> >> - upload everything to a (temporary) repo that the users can define in
> >> their project setup.
> >>
> >> And these steps should be performed for the struts 2 ext as well.
> >>
> >> Now for dependencies definitions, maven has a system of transitive
> >> dependencies, dependencies of dependencies. For example if we take the
> >> pom for struts2-core:
> >> http://www.mvnrepository.com/artifact/org.apache.struts/struts2-
> core/2.1.2
> >> you can see that this artifact depends on a lot of other artifacts.
> >> That was why I was asking you to let me know what the *real*
> >> dependencies are for empire struts2. There is no direct dependency for
> >> ognl I suppose, this is a struts2 dependency, not a empire struts2 ext
> >> one.
> >>
> >> The point is that preparing all the above is easily done when empire
> >> is using using maven for its own build. And that would be step 2. Once
> >> the maven repo is set up we could also transform the DBWebSample to a
> >> maven build (as step 1.5) so that the example can be run using maven.
> >>
> >> Summary: set up a (temp) maven repo + transform sample to maven as
> >> test, or move the whole empire build to maven (big bang)
> >>
> >> Regards,
> >>
> >> Francis
> >
> >
> 
> 
> 
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.

Re: Empire-db and Empire-Struts2-ext distribution with Maven support

[Francis De Brabandere <fr...@gmail.com>]

Rainer,

I'm still not sure we are talking about the same things as you keep
mentioning the 'distribution'... In the maven world your distribution
is uploading artifacts to a maven repository. So for maven users you
want to set up that repository. There is no need to change anything in
the current distribution layout/files. I would only create a pom file
for each artifact and upload that that together with the jar, src jar
and doc jar to a repository. (this will however take time on every
release and we want to keep this period short and go to step 2 [full
maven build] as fast as possible)

The only remaining thing I need here is the *direct* dependencies for
the struts2 ext.

[step 2]
Now if we talk about the source repo (subversion) and you want to
migrate the project to maven the repository should be restructured
(like wicket). As an option you may want to keep the ant build
available (update the build.xml). Once this is taken care of we can
define the "distribution" in the maven build and from then on maven
will generate the distribution file (that can be used by non-maven
users).
see this file for an example distribution configuration:
http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml

I hope I made myself clear this time :-)

Regards,

Francis


On Fri, Nov 28, 2008 at 10:52 PM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> do whatever needs to be done for step 1.
>
> As fas as the distribution layout is concerned I was having a look at other Apache projects and how they do it.
> Take e.g. Apache Wicket (http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1) or Apache CXF (http://cxf.apache.org/download.html)
>
> We should structure our distribution in a similar fashion so that it best fits Maven.
> But if you think that we can leave our layout and just add the pom-files that's fine by me.
>
> I know that the dependencies are not supplied with the Apache Wicket and Apache CXF distribtions but are fechted by Maven.
> The question is, can we still provide the jars in order to allow a simple ant build and leave Maven as an option?
>
> Whatever you do, it should be a good solutions that give the user an adavantage over the existing approach.
> Let me know if I can be of any help.
>
> Regards
> Rainer
>
> P.S. Are you working a lot with databases and have you used Empire-db so far?
>
>
> Francis De Brabandere wrote:
>> Re: Information about the empire-struts2-ext distribution
>>
>> Rainer,
>>
>> Thanks for the info but I don't think we are talking about the same thing.
>> Let's think about what a maven user would like from the empire-db project.
>>
>> As a maven user you declare dependencies to other artifacts (jar's) to
>> have them fetched on build/eclipse project setup time. So what you
>> gain is not having to download a distribution or whatever is used to
>> build the library you want to use. All you do is define where the
>> dependencies' artifacts are located (if not in the central repo) and
>> which they are. What you are talking about is that the user can
>> download the "distribution" and build it including samples using
>> maven. I don't see any value in that, I want to *build my* project
>> using maven and *use your* library without too much
>> configuration/setup.
>>
>> So what are the steps to provide empire as dependency in maven:
>>
>> - Create main jar, source jar, and javadoc jar
>> - Define pom for empire (including definitions of the dependencies)
>> - upload everything to a (temporary) repo that the users can define in
>> their project setup.
>>
>> And these steps should be performed for the struts 2 ext as well.
>>
>> Now for dependencies definitions, maven has a system of transitive
>> dependencies, dependencies of dependencies. For example if we take the
>> pom for struts2-core:
>> http://www.mvnrepository.com/artifact/org.apache.struts/struts2-core/2.1.2
>> you can see that this artifact depends on a lot of other artifacts.
>> That was why I was asking you to let me know what the *real*
>> dependencies are for empire struts2. There is no direct dependency for
>> ognl I suppose, this is a struts2 dependency, not a empire struts2 ext
>> one.
>>
>> The point is that preparing all the above is easily done when empire
>> is using using maven for its own build. And that would be step 2. Once
>> the maven repo is set up we could also transform the DBWebSample to a
>> maven build (as step 1.5) so that the example can be run using maven.
>>
>> Summary: set up a (temp) maven repo + transform sample to maven as
>> test, or move the whole empire build to maven (big bang)
>>
>> Regards,
>>
>> Francis
>
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Empire-db and Empire-Struts2-ext distribution with Maven support

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

do whatever needs to be done for step 1.

As fas as the distribution layout is concerned I was having a look at other Apache projects and how they do it.
Take e.g. Apache Wicket (http://www.apache.org/dyn/closer.cgi/wicket/1.4-rc1) or Apache CXF (http://cxf.apache.org/download.html)

We should structure our distribution in a similar fashion so that it best fits Maven.
But if you think that we can leave our layout and just add the pom-files that's fine by me.

I know that the dependencies are not supplied with the Apache Wicket and Apache CXF distribtions but are fechted by Maven.
The question is, can we still provide the jars in order to allow a simple ant build and leave Maven as an option?

Whatever you do, it should be a good solutions that give the user an adavantage over the existing approach.
Let me know if I can be of any help.

Regards
Rainer

P.S. Are you working a lot with databases and have you used Empire-db so far?


Francis De Brabandere wrote:
> Re: Information about the empire-struts2-ext distribution
>  
> Rainer,
> 
> Thanks for the info but I don't think we are talking about the same thing.
> Let's think about what a maven user would like from the empire-db project.
> 
> As a maven user you declare dependencies to other artifacts (jar's) to
> have them fetched on build/eclipse project setup time. So what you
> gain is not having to download a distribution or whatever is used to
> build the library you want to use. All you do is define where the
> dependencies' artifacts are located (if not in the central repo) and
> which they are. What you are talking about is that the user can
> download the "distribution" and build it including samples using
> maven. I don't see any value in that, I want to *build my* project
> using maven and *use your* library without too much
> configuration/setup.
> 
> So what are the steps to provide empire as dependency in maven:
> 
> - Create main jar, source jar, and javadoc jar
> - Define pom for empire (including definitions of the dependencies)
> - upload everything to a (temporary) repo that the users can define in
> their project setup.
> 
> And these steps should be performed for the struts 2 ext as well.
> 
> Now for dependencies definitions, maven has a system of transitive
> dependencies, dependencies of dependencies. For example if we take the
> pom for struts2-core:
> http://www.mvnrepository.com/artifact/org.apache.struts/struts2-core/2.1.2
> you can see that this artifact depends on a lot of other artifacts.
> That was why I was asking you to let me know what the *real*
> dependencies are for empire struts2. There is no direct dependency for
> ognl I suppose, this is a struts2 dependency, not a empire struts2 ext
> one.
> 
> The point is that preparing all the above is easily done when empire
> is using using maven for its own build. And that would be step 2. Once
> the maven repo is set up we could also transform the DBWebSample to a
> maven build (as step 1.5) so that the example can be run using maven.
> 
> Summary: set up a (temp) maven repo + transform sample to maven as
> test, or move the whole empire build to maven (big bang)
> 
> Regards,
> 
> Francis

Re: Information about the empire-struts2-ext distribution

[Francis De Brabandere <fr...@gmail.com>]

Rainer,

Thanks for the info but I don't think we are talking about the same thing.
Let's think about what a maven user would like from the empire-db project.

As a maven user you declare dependencies to other artifacts (jar's) to
have them fetched on build/eclipse project setup time. So what you
gain is not having to download a distribution or whatever is used to
build the library you want to use. All you do is define where the
dependencies' artifacts are located (if not in the central repo) and
which they are. What you are talking about is that the user can
download the "distribution" and build it including samples using
maven. I don't see any value in that, I want to *build my* project
using maven and *use your* library without too much
configuration/setup.

So what are the steps to provide empire as dependency in maven:

- Create main jar, source jar, and javadoc jar
- Define pom for empire (including definitions of the dependencies)
- upload everything to a (temporary) repo that the users can define in
their project setup.

And these steps should be performed for the struts 2 ext as well.

Now for dependencies definitions, maven has a system of transitive
dependencies, dependencies of dependencies. For example if we take the
pom for struts2-core:
http://www.mvnrepository.com/artifact/org.apache.struts/struts2-core/2.1.2
you can see that this artifact depends on a lot of other artifacts.
That was why I was asking you to let me know what the *real*
dependencies are for empire struts2. There is no direct dependency for
ognl I suppose, this is a struts2 dependency, not a empire struts2 ext
one.

The point is that preparing all the above is easily done when empire
is using using maven for its own build. And that would be step 2. Once
the maven repo is set up we could also transform the DBWebSample to a
maven build (as step 1.5) so that the example can be run using maven.

Summary: set up a (temp) maven repo + transform sample to maven as
test, or move the whole empire build to maven (big bang)

Regards,

Francis



On Wed, Nov 26, 2008 at 9:28 PM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Franics,
>
> as promised I want go give you some detail about the empire-struts2-ext
> distribution files.
> The archive contains both binaries and source code of the strut2-ext library
> as well as a sample application that shows how to use it.
>
> I don't know whether you have tried and mangaged to run the example
> application, but the problem we have at the moment is, that the jars in the
> lib folder which are required to build the struts2-ext-jar from the source
> are also required for the DBWebSample appliation. For the latter however
> they should reside in
> examples\DBWebSample\WebRoot\WEB-INF\lib
>
> Since we did not want to distribute the same files twice, we decided to
> provide a file called copy_jars (.bat and .sh) in the DBWebSamples lib
> folder. This solution however is not ideal.
>
> Building the struts2-ext.jar or the DBWebSample requires the following
> dependencies:
>
> Common stuff:
> -commons-beanutils-1.7.0.jar
> -commons-collections-3.2.1.jar
> -commons-digester-1.8.jar
> -commons-fileupload-1.2.1.jar
> -commons-io-1.4.jar
> -commons-logging-1.0.4.jar
> -log4j-1.2.14.jar
>
> Empire-db:
> -empire-db-2.0.4.jar
>
> JEE-Web Application (taken from Tomcat 5.5)
> -servlet-api.jar
> -jsp-api.jar
>
> Apache Struts2 dependencies:
> -ognl-2.6.11.jar
> -struts2-codebehind-plugin-2.0.11.2.jar
> -struts2-core-2.0.11.2.jar
> -struts2-sitemesh-plugin-2.0.11.2.jar
> -freemarker-2.3.8.jar
> -xwork-2.0.5.jar
>
> Apache Tiles project dependencies:
> -tiles-api-2.0.4.jar
> -tiles-core-2.0.4.jar
> -tiles-jsp-2.0.4.jar
>
> The DBWebSample additionally needs the HSQLDB database
> (hsqldb-1.8.0.10.jar).
>
> Ideally I would still provide all the dependencies with the distribution
> (i.e. put the in a local repository), but organize it in a more convenient
> way, so that the user does not have to copy the jars around.
> With maven it should be possible to create Projects for Eclipse / NetBeans
> and others for both building the empire-struts2-ext.jar from the source as
> well as compile and run the DBWebSample application. The distribution should
> also be laid out in the Maven way (folder structure you suggested).
>
> As proposed, if you could do that and send the result back to me I would
> then make sure, that further distributions are provided that way. I will
> also try to modify the ant scripts to that the user has a choice of Maven or
> Ant.
>
> So I hope you have all the information you need now.
> (If not just ask).
>
> Thanks and best regards
> Rainer
>
> P.S. I'd be interested to know, whether and how you have evaluated or used
> Empire-db and what exactly attracted you to our project.
>
>
> Francis De Brabandere wrote:
>>
>> Re: Maven support for the upcoming 2.0.5 release
>>
>> > This is largely my fault and I want to apologize for that. There are so
>> > many
>> > documents to read and understand and it seems that Jörg and I have been
>> > a
>> > bit too optimistic about the requirements.
>>
>> No problem
>>
>> >
>> > If you are still interested we would still try to get you on as one of
>> > our
>> > committers but we have to get it right this time. This involves an
>> > internal
>> (private) proposal, a vote and the information of the Incubator PMC. I
>> would
>> expect this to take another couple of weeks time.
>> BTW: Have you already have filled out and submitted your Contributor
>> license
>> agreement (ICLA)? If so good, it was not in vain.
>>
>> Yep my ICLA has been sent to secretary@ap... but I did not receive any
>> confirmation.
>>
>> > In the meantime you can, if you want, reorganize and extend the current
>> > distribution for Maven and send the result to me. We will modify our
>> > current
>> > build files to accommodate the changes. I will give you an update about
>> > the
>> > empire-struts2-ext dependencies tomorrow.
>>
>> There is no need to reorganise the distribution. We can just provide
>> pom's for each artefact and a .sh/.bat file to install them in the
>> user's local maven repo. Or we can set up a temporary public
>> repository. That would help out maven users willing to use empire-db.
>>
>> As reorganising the distribution would take a lot of time that is not
>> something to do on every release :-s
>>
>> Regards,
>>
>> Francis
>>
>>
>> >
>> > Sorry again for the inconvenience.
>> >
>> >
>> > Rainer
>> >
>
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Information about the empire-struts2-ext distribution

[Rainer Döbele <do...@esteam.de>]

Hi Franics,

as promised I want go give you some detail about the empire-struts2-ext distribution files.
The archive contains both binaries and source code of the strut2-ext library as well as a sample application that shows how to use it. 

I don't know whether you have tried and mangaged to run the example application, but the problem we have at the moment is, that the jars in the lib folder which are required to build the struts2-ext-jar from the source are also required for the DBWebSample appliation. For the latter however they should reside in 
examples\DBWebSample\WebRoot\WEB-INF\lib

Since we did not want to distribute the same files twice, we decided to provide a file called copy_jars (.bat and .sh) in the DBWebSamples lib folder. This solution however is not ideal.

Building the struts2-ext.jar or the DBWebSample requires the following dependencies:

Common stuff:
-commons-beanutils-1.7.0.jar
-commons-collections-3.2.1.jar
-commons-digester-1.8.jar
-commons-fileupload-1.2.1.jar
-commons-io-1.4.jar
-commons-logging-1.0.4.jar
-log4j-1.2.14.jar

Empire-db:
-empire-db-2.0.4.jar

JEE-Web Application (taken from Tomcat 5.5)
-servlet-api.jar 
-jsp-api.jar

Apache Struts2 dependencies:
-ognl-2.6.11.jar
-struts2-codebehind-plugin-2.0.11.2.jar
-struts2-core-2.0.11.2.jar
-struts2-sitemesh-plugin-2.0.11.2.jar
-freemarker-2.3.8.jar
-xwork-2.0.5.jar

Apache Tiles project dependencies:
-tiles-api-2.0.4.jar
-tiles-core-2.0.4.jar
-tiles-jsp-2.0.4.jar

The DBWebSample additionally needs the HSQLDB database (hsqldb-1.8.0.10.jar).

Ideally I would still provide all the dependencies with the distribution (i.e. put the in a local repository), but organize it in a more convenient way, so that the user does not have to copy the jars around.
With maven it should be possible to create Projects for Eclipse / NetBeans and others for both building the empire-struts2-ext.jar from the source as well as compile and run the DBWebSample application. The distribution should also be laid out in the Maven way (folder structure you suggested).

As proposed, if you could do that and send the result back to me I would then make sure, that further distributions are provided that way. I will also try to modify the ant scripts to that the user has a choice of Maven or Ant.

So I hope you have all the information you need now.
(If not just ask).

Thanks and best regards
Rainer

P.S. I'd be interested to know, whether and how you have evaluated or used Empire-db and what exactly attracted you to our project.


Francis De Brabandere wrote:
> 
> Re: Maven support for the upcoming 2.0.5 release
>  
> > This is largely my fault and I want to apologize for that. There are so many
> > documents to read and understand and it seems that Jörg and I have been a
> > bit too optimistic about the requirements.
> 
> No problem
> 
> >
> > If you are still interested we would still try to get you on as one of our
> > committers but we have to get it right this time. This involves an internal
> (private) proposal, a vote and the information of the Incubator PMC. I would
> expect this to take another couple of weeks time.
> BTW: Have you already have filled out and submitted your Contributor license
> agreement (ICLA)? If so good, it was not in vain.
> 
> Yep my ICLA has been sent to secretary@ap... but I did not receive any
> confirmation.
> 
> > In the meantime you can, if you want, reorganize and extend the current
> > distribution for Maven and send the result to me. We will modify our current
> > build files to accommodate the changes. I will give you an update about the
> > empire-struts2-ext dependencies tomorrow.
> 
> There is no need to reorganise the distribution. We can just provide
> pom's for each artefact and a .sh/.bat file to install them in the
> user's local maven repo. Or we can set up a temporary public
> repository. That would help out maven users willing to use empire-db.
> 
> As reorganising the distribution would take a lot of time that is not
> something to do on every release :-s
> 
> Regards,
> 
> Francis
> 
> 
> >
> > Sorry again for the inconvenience.
> >
> >
> > Rainer
> >

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

> This is largely my fault and I want to apologize for that. There are so many
> documents to read and understand and it seems that Jörg and I have been a
> bit too optimistic about the requirements.

No problem

>
> If you are still interested we would still try to get you on as one of our
> committers but we have to get it right this time. This involves an internal
> (private) proposal, a vote and the information of the Incubator PMC. I would
> expect this to take another couple of weeks time.
> BTW: Have you already have filled out and submitted your Contributor license
> agreement (ICLA)? If so good, it was not in vain.

Yep my ICLA has been sent to secretary@ap... but I did not receive any
confirmation.

> In the meantime you can, if you want, reorganize and extend the current
> distribution for Maven and send the result to me. We will modify our current
> build files to accommodate the changes. I will give you an update about the
> empire-struts2-ext dependencies tomorrow.

There is no need to reorganise the distribution. We can just provide
pom's for each artefact and a .sh/.bat file to install them in the
user's local maven repo. Or we can set up a temporary public
repository. That would help out maven users willing to use empire-db.

As reorganising the distribution would take a lot of time that is not
something to do on every release :-s

Regards,

Francis


>
> Sorry again for the inconvenience.
>
>
> Rainer
>
>>
>> Any updates on me becoming a committer?
>> Who is responsible for empire-db-struts2?
>>
>> On Mon, Nov 17, 2008 at 10:38 AM, Francis De Brabandere
>> <fr...@gmail.com> wrote:
>> > Hi,
>> >
>> > I just read that incubating releases can not be uploaded to the
>> > central maven repository, there is a separate repository available for
>> > those:
>> > http://www.apache.org/dev/repository-faq.html
>> >
>> > Further I need to know what the real dependencies are for
>> > empire-db-struts2, the lib dir also contains transitive dependencies
>> > (dependencies of dependencies) but I should not declare those in the
>> > pom files.
>> >
>> > I set up a temp testing repository at maven.somatik.be
>> >                <repository>
>> >                  <id>maven.somatik.be</id>
>> >                  <name>Somatik Repository for Maven</name>
>> >                  <url>http://maven.somatik.be</url>
>> >                  <layout>default</layout>
>> >                </repository>
>> >
>> > with the following artifact available:
>> > <dependency>
>> >                <groupId>org.apache.empire</groupId>
>> >                <artifactId>empire-db</artifactId>
>> >                <version>2.0.4-incubating</version>
>> >        </dependency>
>> > (source and javadoc jar are not in there yet)
>> >
>> > Is the groupid and artifactid correct?
>> >
>> > Francis
>> >
>
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Dear Francis,

like Jörg has already explained to you we have by mistake not properly followed the Apache guidelines for new committers and one of our mentors has informed us that we cannot get you on this way.

This is largely my fault and I want to apologize for that. There are so many documents to read and understand and it seems that Jörg and I have been a bit too optimistic about the requirements.

If you are still interested we would still try to get you on as one of our committers but we have to get it right this time. This involves an internal (private) proposal, a vote and the information of the Incubator PMC. I would expect this to take another couple of weeks time.
BTW: Have you already have filled out and submitted your Contributor license agreement (ICLA)? If so good, it was not in vain.

In the meantime you can, if you want, reorganize and extend the current distribution for Maven and send the result to me. We will modify our current build files to accommodate the changes. I will give you an update about the empire-struts2-ext dependencies tomorrow.

Sorry again for the inconvenience.


Rainer

>  
> Any updates on me becoming a committer?
> Who is responsible for empire-db-struts2?
> 
> On Mon, Nov 17, 2008 at 10:38 AM, Francis De Brabandere
> <fr...@gmail.com> wrote:
> > Hi,
> >
> > I just read that incubating releases can not be uploaded to the
> > central maven repository, there is a separate repository available for
> > those:
> > http://www.apache.org/dev/repository-faq.html
> >
> > Further I need to know what the real dependencies are for
> > empire-db-struts2, the lib dir also contains transitive dependencies
> > (dependencies of dependencies) but I should not declare those in the
> > pom files.
> >
> > I set up a temp testing repository at maven.somatik.be
> >                <repository>
> >                  <id>maven.somatik.be</id>
> >                  <name>Somatik Repository for Maven</name>
> >                  <url>http://maven.somatik.be</url>
> >                  <layout>default</layout>
> >                </repository>
> >
> > with the following artifact available:
> > <dependency>
> >                <groupId>org.apache.empire</groupId>
> >                <artifactId>empire-db</artifactId>
> >                <version>2.0.4-incubating</version>
> >        </dependency>
> > (source and javadoc jar are not in there yet)
> >
> > Is the groupid and artifactid correct?
> >
> > Francis
> >

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

Any updates on me becoming a committer?
Who is responsible for empire-db-struts2?

On Mon, Nov 17, 2008 at 10:38 AM, Francis De Brabandere
<fr...@gmail.com> wrote:
> Hi,
>
> I just read that incubating releases can not be uploaded to the
> central maven repository, there is a separate repository available for
> those:
> http://www.apache.org/dev/repository-faq.html
>
> Further I need to know what the real dependencies are for
> empire-db-struts2, the lib dir also contains transitive dependencies
> (dependencies of dependencies) but I should not declare those in the
> pom files.
>
> I set up a temp testing repository at maven.somatik.be
>                <repository>
>                  <id>maven.somatik.be</id>
>                  <name>Somatik Repository for Maven</name>
>                  <url>http://maven.somatik.be</url>
>                  <layout>default</layout>
>                </repository>
>
> with the following artifact available:
> <dependency>
>                <groupId>org.apache.empire</groupId>
>                <artifactId>empire-db</artifactId>
>                <version>2.0.4-incubating</version>
>        </dependency>
> (source and javadoc jar are not in there yet)
>
> Is the groupid and artifactid correct?
>
> Francis
>
>
> On Sun, Nov 16, 2008 at 8:33 PM, Rainer Döbele <do...@esteam.de> wrote:
>> Hi Francis,
>>
>> excellent.
>> Hennig (our sponsor) has told me in the meatime how to get you on.
>> We (i.e. the existing Empire-db committers) have to vote you in.
>> Therefore we have to call for a vote and get at least three positive votes
>> (which should not be a problem).
>>
>> Jörg, you're the voting master.
>> Would you be so kind and call for a vote again concering accepting Francis
>> as our new committer?
>>
>> Concering upcoming release 2.0.5.:
>> So far, we have only a few minor bugfixes and small improvements to publish.
>> But the Maven thing would be a good reason to get a new release out.
>>
>> However publishing releases can sometimes be tedious in the incubator.
>> Once we all have accepted the release the Incubator PMC has to accept is as
>> well.
>>
>> We had to fight long and hard to get the previous release accepted due to
>> some legal concerns.
>> That should be better this time around, but you never know.
>>
>> Rainer
>>
>>
>> Francis De Brabandere wrote:
>>>
>>> I'll take care of the Contributor License Agreement this evening.
>>>
>>> > Still I plead for a smooth transition in two phases:
>>> >
>>> > Phase one: Take the current distribution
>>> > (apache-empire-db-2.0.4-incubating
>>> > and apache-empire-struts2-ext-1.0.4-incubating from
>>> > http://www.apache.org/dist/incubator/empire-db) and restructure it for
>>> > Maven
>>> > in a way that it best possibly conforms to all Maven conventions. This
>>> > would
>>> > also include putting all required files into the maven repository. Next
>>> > we
>>> > will change our distribution scripts to build the distribution in that
>>> > way
>>> > for the 2.0.5 release.
>>>
>>> Uploading the current distribution to the central repo should not be a
>>> problem. I'll make the needed pom files and stuff.
>>> (http://maven.apache.org/guides/mini/guide-central-repository-upload.html)
>>>
>>> >
>>> > Phase two: Once the 2.0.5. release is out and everybody had a chance to
>>> > see
>>> > the benefits, we can restructure our internal SVN structure in the same
>>> > way.
>>> >
>>>
>>> Is the 2.0.5 release planned for the near future?
>>>
>>> Regards,
>>>
>>> Francis
>>>
>>> > I hope this approach is feasible and if so I think it is sensible.
>>> > We should possibly consider all options and call for a vote.
>>> >
>>> > Regards
>>> > Rainer
>>> >
>>> > Francis De Brabandere wrote:
>>> >>
>>> >>> Personally I am open for any kind of change if I can see the
>>> >>> advantage.
>>> >>> For
>>> >>> the moment however I would prefer starting with a Maven solution for
>>> >>> the
>>> >>> users of the distribution first, and maybe later on we can change the
>>> >>> internal project layout too.
>>> >>> What do you think?
>>> >>
>>> >> Well the problem is that just creating some pom files without changing
>>> >> the project structure would complicate the maven build a lot. As
>>> >> Martijn said, maven is all about conventions, trying to fight those is
>>> >> looking for trouble. Maven has proven itself and is used by some of
>>> >> the biggest open source java frameworks. The advantage is that when
>>> >> you know how a maven project is structured, you feel at home in any
>>> >> maven based project out there.
>>> >>
>>> >> Users using maven for their build typically don't even care how your
>>> >> project is built or released. All they care about is that the files
>>> >> are available in the central maven repository (or some other public
>>> >> repo) and that all needed dependencies are configured correctly. For
>>> >> them the distribution you are talking about is not needed: the source,
>>> >> binaries and javadoc will be fetched during the initial build and set
>>> >> up in their ide.  The first thing I do when some of my projects need
>>> >> and extra dependency is looking it up on http://www.mvnrepository.com/
>>> >> (I even use their RSS feed to keep myself up to date on the new
>>> >> releases for java related frameworks)
>>> >>
>>> >> Maven is able to perform the task of both build files you described.
>>> >> Distribution files can be built using the assembly plugin (ex
>>> >> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
>>> >>
>>> >> Francis
>>> >>
>>
>
>
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

Hi,

I just read that incubating releases can not be uploaded to the
central maven repository, there is a separate repository available for
those:
http://www.apache.org/dev/repository-faq.html

Further I need to know what the real dependencies are for
empire-db-struts2, the lib dir also contains transitive dependencies
(dependencies of dependencies) but I should not declare those in the
pom files.

I set up a temp testing repository at maven.somatik.be
		<repository>
		  <id>maven.somatik.be</id>
		  <name>Somatik Repository for Maven</name>
		  <url>http://maven.somatik.be</url>
		  <layout>default</layout>
		</repository>

with the following artifact available:
<dependency>
        	<groupId>org.apache.empire</groupId>
        	<artifactId>empire-db</artifactId>
        	<version>2.0.4-incubating</version>
        </dependency>
(source and javadoc jar are not in there yet)

Is the groupid and artifactid correct?

Francis


On Sun, Nov 16, 2008 at 8:33 PM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> excellent.
> Hennig (our sponsor) has told me in the meatime how to get you on.
> We (i.e. the existing Empire-db committers) have to vote you in.
> Therefore we have to call for a vote and get at least three positive votes
> (which should not be a problem).
>
> Jörg, you're the voting master.
> Would you be so kind and call for a vote again concering accepting Francis
> as our new committer?
>
> Concering upcoming release 2.0.5.:
> So far, we have only a few minor bugfixes and small improvements to publish.
> But the Maven thing would be a good reason to get a new release out.
>
> However publishing releases can sometimes be tedious in the incubator.
> Once we all have accepted the release the Incubator PMC has to accept is as
> well.
>
> We had to fight long and hard to get the previous release accepted due to
> some legal concerns.
> That should be better this time around, but you never know.
>
> Rainer
>
>
> Francis De Brabandere wrote:
>>
>> I'll take care of the Contributor License Agreement this evening.
>>
>> > Still I plead for a smooth transition in two phases:
>> >
>> > Phase one: Take the current distribution
>> > (apache-empire-db-2.0.4-incubating
>> > and apache-empire-struts2-ext-1.0.4-incubating from
>> > http://www.apache.org/dist/incubator/empire-db) and restructure it for
>> > Maven
>> > in a way that it best possibly conforms to all Maven conventions. This
>> > would
>> > also include putting all required files into the maven repository. Next
>> > we
>> > will change our distribution scripts to build the distribution in that
>> > way
>> > for the 2.0.5 release.
>>
>> Uploading the current distribution to the central repo should not be a
>> problem. I'll make the needed pom files and stuff.
>> (http://maven.apache.org/guides/mini/guide-central-repository-upload.html)
>>
>> >
>> > Phase two: Once the 2.0.5. release is out and everybody had a chance to
>> > see
>> > the benefits, we can restructure our internal SVN structure in the same
>> > way.
>> >
>>
>> Is the 2.0.5 release planned for the near future?
>>
>> Regards,
>>
>> Francis
>>
>> > I hope this approach is feasible and if so I think it is sensible.
>> > We should possibly consider all options and call for a vote.
>> >
>> > Regards
>> > Rainer
>> >
>> > Francis De Brabandere wrote:
>> >>
>> >>> Personally I am open for any kind of change if I can see the
>> >>> advantage.
>> >>> For
>> >>> the moment however I would prefer starting with a Maven solution for
>> >>> the
>> >>> users of the distribution first, and maybe later on we can change the
>> >>> internal project layout too.
>> >>> What do you think?
>> >>
>> >> Well the problem is that just creating some pom files without changing
>> >> the project structure would complicate the maven build a lot. As
>> >> Martijn said, maven is all about conventions, trying to fight those is
>> >> looking for trouble. Maven has proven itself and is used by some of
>> >> the biggest open source java frameworks. The advantage is that when
>> >> you know how a maven project is structured, you feel at home in any
>> >> maven based project out there.
>> >>
>> >> Users using maven for their build typically don't even care how your
>> >> project is built or released. All they care about is that the files
>> >> are available in the central maven repository (or some other public
>> >> repo) and that all needed dependencies are configured correctly. For
>> >> them the distribution you are talking about is not needed: the source,
>> >> binaries and javadoc will be fetched during the initial build and set
>> >> up in their ide.  The first thing I do when some of my projects need
>> >> and extra dependency is looking it up on http://www.mvnrepository.com/
>> >> (I even use their RSS feed to keep myself up to date on the new
>> >> releases for java related frameworks)
>> >>
>> >> Maven is able to perform the task of both build files you described.
>> >> Distribution files can be built using the assembly plugin (ex
>> >> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
>> >>
>> >> Francis
>> >>
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

excellent. 
Hennig (our sponsor) has told me in the meatime how to get you on.
We (i.e. the existing Empire-db committers) have to vote you in.
Therefore we have to call for a vote and get at least three positive votes (which should not be a problem).

Jörg, you're the voting master. 
Would you be so kind and call for a vote again concering accepting Francis as our new committer?

Concering upcoming release 2.0.5.:
So far, we have only a few minor bugfixes and small improvements to publish.
But the Maven thing would be a good reason to get a new release out.

However publishing releases can sometimes be tedious in the incubator.
Once we all have accepted the release the Incubator PMC has to accept is as well.

We had to fight long and hard to get the previous release accepted due to some legal concerns.
That should be better this time around, but you never know.

Rainer


Francis De Brabandere wrote:
>  
> I'll take care of the Contributor License Agreement this evening.
> 
> > Still I plead for a smooth transition in two phases:
> >
> > Phase one: Take the current distribution (apache-empire-db-2.0.4-incubating
> > and apache-empire-struts2-ext-1.0.4-incubating from
> > http://www.apache.org/dist/incubator/empire-db) and restructure it for Maven
> > in a way that it best possibly conforms to all Maven conventions. This would
> > also include putting all required files into the maven repository. Next we
> > will change our distribution scripts to build the distribution in that way
> > for the 2.0.5 release.
> 
> Uploading the current distribution to the central repo should not be a
> problem. I'll make the needed pom files and stuff.
> (http://maven.apache.org/guides/mini/guide-central-repository-upload.html)
> 
> >
> > Phase two: Once the 2.0.5. release is out and everybody had a chance to see
> > the benefits, we can restructure our internal SVN structure in the same way.
> >
> 
> Is the 2.0.5 release planned for the near future?
> 
> Regards,
> 
> Francis
> 
> > I hope this approach is feasible and if so I think it is sensible.
> > We should possibly consider all options and call for a vote.
> >
> > Regards
> > Rainer
> >
> > Francis De Brabandere wrote:
> >>
> >>> Personally I am open for any kind of change if I can see the advantage.
> >>> For
> >>> the moment however I would prefer starting with a Maven solution for the
> >>> users of the distribution first, and maybe later on we can change the
> >>> internal project layout too.
> >>> What do you think?
> >>
> >> Well the problem is that just creating some pom files without changing
> >> the project structure would complicate the maven build a lot. As
> >> Martijn said, maven is all about conventions, trying to fight those is
> >> looking for trouble. Maven has proven itself and is used by some of
> >> the biggest open source java frameworks. The advantage is that when
> >> you know how a maven project is structured, you feel at home in any
> >> maven based project out there.
> >>
> >> Users using maven for their build typically don't even care how your
> >> project is built or released. All they care about is that the files
> >> are available in the central maven repository (or some other public
> >> repo) and that all needed dependencies are configured correctly. For
> >> them the distribution you are talking about is not needed: the source,
> >> binaries and javadoc will be fetched during the initial build and set
> >> up in their ide.  The first thing I do when some of my projects need
> >> and extra dependency is looking it up on http://www.mvnrepository.com/
> >> (I even use their RSS feed to keep myself up to date on the new
> >> releases for java related frameworks)
> >>
> >> Maven is able to perform the task of both build files you described.
> >> Distribution files can be built using the assembly plugin (ex
> >> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
> >>
> >> Francis
> >>

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

excellent. 
Hennig (our sponsor) has told me in the meatime how to get you on.
We (i.e. the existing Empire-db committers) have to vote you in.
Therefore we have to call for a vote and get at least three positive votes (which should not be a problem).

Jörg, you're the voting master. 
Would you be so kind and call for a vote again concering accepting Francis as our new committer?

Concering upcoming release 2.0.5.:
So far, we have only a few minor bugfixes and small improvements to publish.
But the Maven thing would be a good reason to get a new release out.

However publishing releases can sometimes be tedious in the incubator.
Once we all have accepted the release the Incubator PMC has to accept is as well.

We had to fight long and hard to get the previous release accepted due to some legal concerns.
That should be better this time around, but you never know.

Rainer


Francis De Brabandere wrote:
>  
> I'll take care of the Contributor License Agreement this evening.
> 
> > Still I plead for a smooth transition in two phases:
> >
> > Phase one: Take the current distribution (apache-empire-db-2.0.4-incubating
> > and apache-empire-struts2-ext-1.0.4-incubating from
> > http://www.apache.org/dist/incubator/empire-db) and restructure it for Maven
> > in a way that it best possibly conforms to all Maven conventions. This would
> > also include putting all required files into the maven repository. Next we
> > will change our distribution scripts to build the distribution in that way
> > for the 2.0.5 release.
> 
> Uploading the current distribution to the central repo should not be a
> problem. I'll make the needed pom files and stuff.
> (http://maven.apache.org/guides/mini/guide-central-repository-upload.html)
> 
> >
> > Phase two: Once the 2.0.5. release is out and everybody had a chance to see
> > the benefits, we can restructure our internal SVN structure in the same way.
> >
> 
> Is the 2.0.5 release planned for the near future?
> 
> Regards,
> 
> Francis
> 
> > I hope this approach is feasible and if so I think it is sensible.
> > We should possibly consider all options and call for a vote.
> >
> > Regards
> > Rainer
> >
> > Francis De Brabandere wrote:
> >>
> >>> Personally I am open for any kind of change if I can see the advantage.
> >>> For
> >>> the moment however I would prefer starting with a Maven solution for the
> >>> users of the distribution first, and maybe later on we can change the
> >>> internal project layout too.
> >>> What do you think?
> >>
> >> Well the problem is that just creating some pom files without changing
> >> the project structure would complicate the maven build a lot. As
> >> Martijn said, maven is all about conventions, trying to fight those is
> >> looking for trouble. Maven has proven itself and is used by some of
> >> the biggest open source java frameworks. The advantage is that when
> >> you know how a maven project is structured, you feel at home in any
> >> maven based project out there.
> >>
> >> Users using maven for their build typically don't even care how your
> >> project is built or released. All they care about is that the files
> >> are available in the central maven repository (or some other public
> >> repo) and that all needed dependencies are configured correctly. For
> >> them the distribution you are talking about is not needed: the source,
> >> binaries and javadoc will be fetched during the initial build and set
> >> up in their ide.  The first thing I do when some of my projects need
> >> and extra dependency is looking it up on http://www.mvnrepository.com/
> >> (I even use their RSS feed to keep myself up to date on the new
> >> releases for java related frameworks)
> >>
> >> Maven is able to perform the task of both build files you described.
> >> Distribution files can be built using the assembly plugin (ex
> >> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
> >>
> >> Francis
> >>

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

I'll take care of the Contributor License Agreement this evening.

> Still I plead for a smooth transition in two phases:
>
> Phase one: Take the current distribution (apache-empire-db-2.0.4-incubating
> and apache-empire-struts2-ext-1.0.4-incubating from
> http://www.apache.org/dist/incubator/empire-db) and restructure it for Maven
> in a way that it best possibly conforms to all Maven conventions. This would
> also include putting all required files into the maven repository. Next we
> will change our distribution scripts to build the distribution in that way
> for the 2.0.5 release.

Uploading the current distribution to the central repo should not be a
problem. I'll make the needed pom files and stuff.
(http://maven.apache.org/guides/mini/guide-central-repository-upload.html)

>
> Phase two: Once the 2.0.5. release is out and everybody had a chance to see
> the benefits, we can restructure our internal SVN structure in the same way.
>

Is the 2.0.5 release planned for the near future?

Regards,

Francis

> I hope this approach is feasible and if so I think it is sensible.
> We should possibly consider all options and call for a vote.
>
> Regards
> Rainer
>
> Francis De Brabandere wrote:
>>
>>> Personally I am open for any kind of change if I can see the advantage.
>>> For
>>> the moment however I would prefer starting with a Maven solution for the
>>> users of the distribution first, and maybe later on we can change the
>>> internal project layout too.
>>> What do you think?
>>
>> Well the problem is that just creating some pom files without changing
>> the project structure would complicate the maven build a lot. As
>> Martijn said, maven is all about conventions, trying to fight those is
>> looking for trouble. Maven has proven itself and is used by some of
>> the biggest open source java frameworks. The advantage is that when
>> you know how a maven project is structured, you feel at home in any
>> maven based project out there.
>>
>> Users using maven for their build typically don't even care how your
>> project is built or released. All they care about is that the files
>> are available in the central maven repository (or some other public
>> repo) and that all needed dependencies are configured correctly. For
>> them the distribution you are talking about is not needed: the source,
>> binaries and javadoc will be fetched during the initial build and set
>> up in their ide.  The first thing I do when some of my projects need
>> and extra dependency is looking it up on http://www.mvnrepository.com/
>> (I even use their RSS feed to keep myself up to date on the new
>> releases for java related frameworks)
>>
>> Maven is able to perform the task of both build files you described.
>> Distribution files can be built using the assembly plugin (ex
>> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
>>
>> Francis
>>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

I'll take care of the Contributor License Agreement this evening.

> Still I plead for a smooth transition in two phases:
>
> Phase one: Take the current distribution (apache-empire-db-2.0.4-incubating
> and apache-empire-struts2-ext-1.0.4-incubating from
> http://www.apache.org/dist/incubator/empire-db) and restructure it for Maven
> in a way that it best possibly conforms to all Maven conventions. This would
> also include putting all required files into the maven repository. Next we
> will change our distribution scripts to build the distribution in that way
> for the 2.0.5 release.

Uploading the current distribution to the central repo should not be a
problem. I'll make the needed pom files and stuff.
(http://maven.apache.org/guides/mini/guide-central-repository-upload.html)

>
> Phase two: Once the 2.0.5. release is out and everybody had a chance to see
> the benefits, we can restructure our internal SVN structure in the same way.
>

Is the 2.0.5 release planned for the near future?

Regards,

Francis

> I hope this approach is feasible and if so I think it is sensible.
> We should possibly consider all options and call for a vote.
>
> Regards
> Rainer
>
> Francis De Brabandere wrote:
>>
>>> Personally I am open for any kind of change if I can see the advantage.
>>> For
>>> the moment however I would prefer starting with a Maven solution for the
>>> users of the distribution first, and maybe later on we can change the
>>> internal project layout too.
>>> What do you think?
>>
>> Well the problem is that just creating some pom files without changing
>> the project structure would complicate the maven build a lot. As
>> Martijn said, maven is all about conventions, trying to fight those is
>> looking for trouble. Maven has proven itself and is used by some of
>> the biggest open source java frameworks. The advantage is that when
>> you know how a maven project is structured, you feel at home in any
>> maven based project out there.
>>
>> Users using maven for their build typically don't even care how your
>> project is built or released. All they care about is that the files
>> are available in the central maven repository (or some other public
>> repo) and that all needed dependencies are configured correctly. For
>> them the distribution you are talking about is not needed: the source,
>> binaries and javadoc will be fetched during the initial build and set
>> up in their ide.  The first thing I do when some of my projects need
>> and extra dependency is looking it up on http://www.mvnrepository.com/
>> (I even use their RSS feed to keep myself up to date on the new
>> releases for java related frameworks)
>>
>> Maven is able to perform the task of both build files you described.
>> Distribution files can be built using the assembly plugin (ex
>> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
>>
>> Francis
>>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Martijn Dashorst wrote:
> 
> What is the perceived difference between users and yourself in
> building the distribution files?
> 

for each accepted release we build the distribuion files (all files in http://www.apache.org/dist/incubator/empire-db) that the user can download, including the binaries, the sources, the examples and the documentation.
Currently we do this by running an Ant script.

The user never builds a distribution, but the distribution contains a script to build the binaries from the source.
This is currently also an Ant script but a different one obiously.
And this his where we want to provide Maven support.

Rainer

Re: Maven support for the upcoming 2.0.5 release

[Martijn Dashorst <ma...@gmail.com>]

What is the perceived difference between users and yourself in
building the distribution files?

Martijn

On Thu, Nov 13, 2008 at 3:01 PM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> What I mean by maven support is that we want users to be able to build the distribution files (i.e. apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating in http://www.apache.org/dist/incubator/empire-db) with Maven.
> Also it should provide projects files for Eclipse, Net Beans etc. if possible so that we don't have to supply them with the distribution.
>
> The build.xml Ant file supplied with the distribution could possibly remain and still work (giving the user an option).
>
> We don't need Maven for our own development or to build the distribution.
> (Unless you can convince us that it's worthwhile)
>
> Is that how you understood it?
>
> Regards,
> Rainer
>
>
> Francis De Brabandere wrote:
>> Betreff: Re: Maven support for the upcoming 2.0.5 release
>>
>> Do I understand correctly that you want to start building the project
>> using maven instead of ant? Because you are talking about maven
>> 'support'...
>>
>> On Thu, Nov 13, 2008 at 12:54 PM, Rainer Döbele <do...@esteam.de> wrote:
>> > Thanks a lot Francis,
>> >
>> > I have submitted all my recent changes and I have no local changes left.
>> > Matt and Manuel should not have local changes as far as I know.
>> >
>> > There is one JIRA task still open from Jörg (EMPIREDB-27).
>> > Jörg can you please tell us whether or not you are currently working on
>> this issue?
>> >
>> > I have created a new JIRA-Task for the MAVEN support.
>> > See https://issues.apache.org/jira/browse/EMPIREDB-29
>> > Please use EMPIREDB-29 in your comment when you check in modified files.
>> >
>> > Regards,
>> > Rainer
>> >
>> > Francis De Brabandere wrote:
>> >>
>> >> Is there a lot of activity in subversion at the moment? The switch
>> >> should take about an evening of work (CET (UTC+1)). Are there any
>> >> active branches?
>> >> I'm willing to set everything up but you need to make sure nobody has
>> >> local modifications since everything is going to be moved.
>> >>
>> >> Francis
>> >>
>> >> On Tue, Nov 11, 2008 at 12:22 PM, Francis De Brabandere
>> >> <fr...@gmail.com> wrote:
>> >> > Hi,
>> >> >
>> >> > The first step for moving to maven is always moving everything into
>> >> > the maven layout and updating the ant scripts. This if you want a
>> >> > gradual migration.
>> >> > http://maven.apache.org/guides/introduction/introduction-to-the-
>> >> standard-directory-layout.html
>> >> >
>> >> > I suppose there will be one parent module, one main empire-db module,
>> >> > the struts integration module and some example modules
>> >> >
>> >> > Regards,
>> >> >
>> >> > Francis
>> >> >
>> >> > On Tue, Nov 11, 2008 at 11:48 AM, Jörg Reiher <re...@esteam.de>
>> wrote:
>> >> >> Hi Francis,
>> >> >> first thanks for reporting the bug in the SampleConfig - that's
>> >> definitely a good start to contribute :-)!
>> >> >>
>> >> >> As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5
>> of
>> >> struts extension respectively) should be to "mavenize" the empire-db
>> >> source code.
>> >> >> This doesn't require deep insight into empire-db, but a good
>> knowledge
>> >> of Maven. So if you feel comfortable with Maven (or you want to get
>> >> comfortable :-) then this would be great.
>> >> >> To start I'd look into other Apache (Incubator) projects to see how
>> >> they used Maven. By "mavenizing" empire-db we could get rid of some
>> >> dependencies and we'd overcome the trouble with
>> >> >> proprietary db drivers, because the user could download them from
>> the
>> >> Maven repository (we can't provide proprietary drivers in the Apache
>> svn
>> >> of course).
>> >> >>
>> >> >> There are a lot of other things that could be done for empire-db
>> that
>> >> need some more insight into the code, for example:
>> >> >> - Implementing drivers for other databases (DerbyDB comes to mind as
>> >> it's also an Apache project)
>> >> >> -> a starting point would be to take a closer look at the *Driver*
>> >> classes in the empire-db project, maybe even starting with a copy of
>> one
>> >> of these as a "template"
>> >> >> - Searching and reporting bugs and/or improvements
>> >> >> - Creating "extensions" for other web/gui frameworks to leverage the
>> >> meta data provided by empire-db
>> >> >> -> this is of course quite time consuming and needs quite good
>> >> knowledge of the empire-db components and the targeted web/gui
>> framework
>> >> >>
>> >> >> So far,
>> >> >> I hope I could help a little bit
>> >> >> any contribution and questions are welcome,
>> >> >> so don't hesitate to post it here
>> >> >>
>> >> >> Greetings
>> >> >> jorg
>> >> >>
>> >> >>> -----Ursprüngliche Nachricht-----
>> >> >>> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
>> >> >>> Gesendet: Sonntag, 9. November 2008 17:20
>> >> >>> An: empire-db-user@incubator.apache.org
>> >> >>> Cc: empire-db-dev@incubator.apache.org
>> >> >>> Betreff: Re: Maven support for the upcoming 2.0.5 release
>> >> >>>
>> >> >>> I might be willing to help out but I have not even tried empire-db
>> >> >>> yet... What kind of skills are you looking for?
>> >> >>>
>> >> >>> Regards
>> >> >>>
>> >> >>> Francis
>> >> >>>
>> >> >>> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
>> >> >>> wrote:
>> >> >>> > For the upcoming Empire-db 2.0.5. release we plan to provide
>> Maven
>> >> >>> support.
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > We are however still struggling to find someone with good Maven
>> >> >>> skills who is willing to help us with that task.
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > So if anyone out there is good with Maven and has the time and
>> will
>> >> >>> to support us, we would very much appreciate to hear from you.
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > Rainer
>> >> >>> >
>> >> >>> >
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> http://www.somatik.be
>> >> >>> Microsoft gives you windows, Linux gives you the whole house.
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > http://www.somatik.be
>> >> > Microsoft gives you windows, Linux gives you the whole house.
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://www.somatik.be
>> >> Microsoft gives you windows, Linux gives you the whole house.
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

you really seem to have a sound knowledge of Maven and know what you are talking about.
That is good and exactly what we need.

I very much appreciate that you want to contribute to our project and you are welcome to be a committer on our project. In order to become a committer you first have to fill out and submit a Contributor License Agreement (see http://www.apache.org/licenses/#clas). I am not quite sure who is going to put you on the project committer list and grant the access privileges - you may want to ask Henning (henning@apache.org) or Martijn (dashorst@apache.org).

I think basically we are all committed of doing it the Maven way, but for me the questions remains on how far how fast.

What I am still a bit concerned about, is that we will face problems in the transition phase and that it will be harder for us to make changes and to publish a new release. Setting it all up the way it is working now took quite a bit of effort and I don't think it'll be that easy to get everything right with Maven immediately. Especially since none of us other committers is really familiar with Maven so far (although we're willing to learn).

Still I plead for a smooth transition in two phases:

Phase one: Take the current distribution (apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating from http://www.apache.org/dist/incubator/empire-db) and restructure it for Maven in a way that it best possibly conforms to all Maven conventions. This would also include putting all required files into the maven repository. Next we will change our distribution scripts to build the distribution in that way for the 2.0.5 release.

Phase two: Once the 2.0.5. release is out and everybody had a chance to see the benefits, we can restructure our internal SVN structure in the same way.

I hope this approach is feasible and if so I think it is sensible.
We should possibly consider all options and call for a vote.

Regards
Rainer

Francis De Brabandere wrote:
> 
>> Personally I am open for any kind of change if I can see the advantage. For
>> the moment however I would prefer starting with a Maven solution for the
>> users of the distribution first, and maybe later on we can change the
>> internal project layout too.
>> What do you think?
> 
> Well the problem is that just creating some pom files without changing
> the project structure would complicate the maven build a lot. As
> Martijn said, maven is all about conventions, trying to fight those is
> looking for trouble. Maven has proven itself and is used by some of
> the biggest open source java frameworks. The advantage is that when
> you know how a maven project is structured, you feel at home in any
> maven based project out there.
> 
> Users using maven for their build typically don't even care how your
> project is built or released. All they care about is that the files
> are available in the central maven repository (or some other public
> repo) and that all needed dependencies are configured correctly. For
> them the distribution you are talking about is not needed: the source,
> binaries and javadoc will be fetched during the initial build and set
> up in their ide.  The first thing I do when some of my projects need
> and extra dependency is looking it up on http://www.mvnrepository.com/
> (I even use their RSS feed to keep myself up to date on the new
> releases for java related frameworks)
> 
> Maven is able to perform the task of both build files you described.
> Distribution files can be built using the assembly plugin (ex
> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
> 
> Francis
> 

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

you really seem to have a sound knowledge of Maven and know what you are talking about.
That is good and exactly what we need.

I very much appreciate that you want to contribute to our project and you are welcome to be a committer on our project. In order to become a committer you first have to fill out and submit a Contributor License Agreement (see http://www.apache.org/licenses/#clas). I am not quite sure who is going to put you on the project committer list and grant the access privileges - you may want to ask Henning (henning@apache.org) or Martijn (dashorst@apache.org).

I think basically we are all committed of doing it the Maven way, but for me the questions remains on how far how fast.

What I am still a bit concerned about, is that we will face problems in the transition phase and that it will be harder for us to make changes and to publish a new release. Setting it all up the way it is working now took quite a bit of effort and I don't think it'll be that easy to get everything right with Maven immediately. Especially since none of us other committers is really familiar with Maven so far (although we're willing to learn).

Still I plead for a smooth transition in two phases:

Phase one: Take the current distribution (apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating from http://www.apache.org/dist/incubator/empire-db) and restructure it for Maven in a way that it best possibly conforms to all Maven conventions. This would also include putting all required files into the maven repository. Next we will change our distribution scripts to build the distribution in that way for the 2.0.5 release.

Phase two: Once the 2.0.5. release is out and everybody had a chance to see the benefits, we can restructure our internal SVN structure in the same way.

I hope this approach is feasible and if so I think it is sensible.
We should possibly consider all options and call for a vote.

Regards
Rainer

Francis De Brabandere wrote:
> 
>> Personally I am open for any kind of change if I can see the advantage. For
>> the moment however I would prefer starting with a Maven solution for the
>> users of the distribution first, and maybe later on we can change the
>> internal project layout too.
>> What do you think?
> 
> Well the problem is that just creating some pom files without changing
> the project structure would complicate the maven build a lot. As
> Martijn said, maven is all about conventions, trying to fight those is
> looking for trouble. Maven has proven itself and is used by some of
> the biggest open source java frameworks. The advantage is that when
> you know how a maven project is structured, you feel at home in any
> maven based project out there.
> 
> Users using maven for their build typically don't even care how your
> project is built or released. All they care about is that the files
> are available in the central maven repository (or some other public
> repo) and that all needed dependencies are configured correctly. For
> them the distribution you are talking about is not needed: the source,
> binaries and javadoc will be fetched during the initial build and set
> up in their ide.  The first thing I do when some of my projects need
> and extra dependency is looking it up on http://www.mvnrepository.com/
> (I even use their RSS feed to keep myself up to date on the new
> releases for java related frameworks)
> 
> Maven is able to perform the task of both build files you described.
> Distribution files can be built using the assembly plugin (ex
> http://svn.apache.org/repos/asf/wicket/trunk/wicket-assembly-all.xml).
> 
> Francis
> 

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

first of all we all use Eclipse and the projects as they are in SVN at the moment are Eclipse projects (with the eclipse files also checked in). So if you just check out all projects under core and those under struts2-ext in one workspace you can compile and run them all.

I know that Maven can generate project files for Eclipse, NetBeans and possibly others and this is why I think it would be a good idea to provide Maven pom file(s) with the distribution.
You are right, that maintaining two build systems would require more work, although I don't think that they would change very frequently. Getting rid of the old Ant script is certainly an option.

When I thought about Maven support however, I wasn’t thinking of changing the internal project structure as it currently is in SVN, since this is not the structure the user will see when downloading the distribution files anyway. Instead the buildRelease.xml Ant script creates the final structure of the distribution. Hence the directory structure you proposed can be provided by changing the buildRelease.xml Ant script accordingly.

So I thought all we need to do is to provide Maven pom files and change the buildRelease.xml script. 

I am still not sure, what benefits the change of the internal project structure as currently in SVN would have for us. Since the projects files of the Empire-db internal development ant those provided with the distribution are somewhat different (e.g. regarding project dependencies and classpath) I assume so would the Maven POM files. Hence there have to be two sets of files anyway. 

Personally I am open for any kind of change if I can see the advantage. For the moment however I would prefer starting with a Maven solution for the users of the distribution first, and maybe later on we can change the internal project layout too.
What do you think?

Rainer

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

On Thu, Nov 13, 2008 at 3:01 PM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> What I mean by maven support is that we want users to be able to build the distribution files (i.e. apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating in http://www.apache.org/dist/incubator/empire-db) with Maven.

If you want users to be able to perform a build using maven then the
changes I proposed are needed

> Also it should provide projects files for Eclipse, Net Beans etc. if possible so that we don't have to supply them with the distribution.

There is no need for eclipse project files in subversion as they can
be generated by maven (mvn eclipse:eclipse and import the projects
into your workspace)
For netbeans you can just install the maven plugin and he will
recognize the pom files as netbeans projects.

> The build.xml Ant file supplied with the distribution could possibly remain and still work (giving the user an option).

That is an option but it is more work to keep two build systems up to
date. For example all lib folders can be removed when using maven but
are still needed for building with ant. But then as I said we can just
update the scripts (paths & stuff) for a transition period.

> We don't need Maven for our own development or to build the distribution.
> (Unless you can convince us that it's worthwhile)

Most people just generate the eclipse project files and use eclipse
for development. Unit tests, deployment, daily builds, style
conformity testing and a lot more can be automated using maven + a
continuous build system like hudson.

What is the dev environment of the current empire-db team?

Regards,

Francis

>
> Is that how you understood it?
>
> Regards,
> Rainer
>
>
> Francis De Brabandere wrote:
>> Betreff: Re: Maven support for the upcoming 2.0.5 release
>>
>> Do I understand correctly that you want to start building the project
>> using maven instead of ant? Because you are talking about maven
>> 'support'...
>>
>> On Thu, Nov 13, 2008 at 12:54 PM, Rainer Döbele <do...@esteam.de> wrote:
>> > Thanks a lot Francis,
>> >
>> > I have submitted all my recent changes and I have no local changes left.
>> > Matt and Manuel should not have local changes as far as I know.
>> >
>> > There is one JIRA task still open from Jörg (EMPIREDB-27).
>> > Jörg can you please tell us whether or not you are currently working on
>> this issue?
>> >
>> > I have created a new JIRA-Task for the MAVEN support.
>> > See https://issues.apache.org/jira/browse/EMPIREDB-29
>> > Please use EMPIREDB-29 in your comment when you check in modified files.
>> >
>> > Regards,
>> > Rainer
>> >
>> > Francis De Brabandere wrote:
>> >>
>> >> Is there a lot of activity in subversion at the moment? The switch
>> >> should take about an evening of work (CET (UTC+1)). Are there any
>> >> active branches?
>> >> I'm willing to set everything up but you need to make sure nobody has
>> >> local modifications since everything is going to be moved.
>> >>
>> >> Francis
>> >>
>> >> On Tue, Nov 11, 2008 at 12:22 PM, Francis De Brabandere
>> >> <fr...@gmail.com> wrote:
>> >> > Hi,
>> >> >
>> >> > The first step for moving to maven is always moving everything into
>> >> > the maven layout and updating the ant scripts. This if you want a
>> >> > gradual migration.
>> >> > http://maven.apache.org/guides/introduction/introduction-to-the-
>> >> standard-directory-layout.html
>> >> >
>> >> > I suppose there will be one parent module, one main empire-db module,
>> >> > the struts integration module and some example modules
>> >> >
>> >> > Regards,
>> >> >
>> >> > Francis
>> >> >
>> >> > On Tue, Nov 11, 2008 at 11:48 AM, Jörg Reiher <re...@esteam.de>
>> wrote:
>> >> >> Hi Francis,
>> >> >> first thanks for reporting the bug in the SampleConfig - that's
>> >> definitely a good start to contribute :-)!
>> >> >>
>> >> >> As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5
>> of
>> >> struts extension respectively) should be to "mavenize" the empire-db
>> >> source code.
>> >> >> This doesn't require deep insight into empire-db, but a good
>> knowledge
>> >> of Maven. So if you feel comfortable with Maven (or you want to get
>> >> comfortable :-) then this would be great.
>> >> >> To start I'd look into other Apache (Incubator) projects to see how
>> >> they used Maven. By "mavenizing" empire-db we could get rid of some
>> >> dependencies and we'd overcome the trouble with
>> >> >> proprietary db drivers, because the user could download them from
>> the
>> >> Maven repository (we can't provide proprietary drivers in the Apache
>> svn
>> >> of course).
>> >> >>
>> >> >> There are a lot of other things that could be done for empire-db
>> that
>> >> need some more insight into the code, for example:
>> >> >> - Implementing drivers for other databases (DerbyDB comes to mind as
>> >> it's also an Apache project)
>> >> >> -> a starting point would be to take a closer look at the *Driver*
>> >> classes in the empire-db project, maybe even starting with a copy of
>> one
>> >> of these as a "template"
>> >> >> - Searching and reporting bugs and/or improvements
>> >> >> - Creating "extensions" for other web/gui frameworks to leverage the
>> >> meta data provided by empire-db
>> >> >> -> this is of course quite time consuming and needs quite good
>> >> knowledge of the empire-db components and the targeted web/gui
>> framework
>> >> >>
>> >> >> So far,
>> >> >> I hope I could help a little bit
>> >> >> any contribution and questions are welcome,
>> >> >> so don't hesitate to post it here
>> >> >>
>> >> >> Greetings
>> >> >> jorg
>> >> >>
>> >> >>> -----Ursprüngliche Nachricht-----
>> >> >>> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
>> >> >>> Gesendet: Sonntag, 9. November 2008 17:20
>> >> >>> An: empire-db-user@incubator.apache.org
>> >> >>> Cc: empire-db-dev@incubator.apache.org
>> >> >>> Betreff: Re: Maven support for the upcoming 2.0.5 release
>> >> >>>
>> >> >>> I might be willing to help out but I have not even tried empire-db
>> >> >>> yet... What kind of skills are you looking for?
>> >> >>>
>> >> >>> Regards
>> >> >>>
>> >> >>> Francis
>> >> >>>
>> >> >>> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
>> >> >>> wrote:
>> >> >>> > For the upcoming Empire-db 2.0.5. release we plan to provide
>> Maven
>> >> >>> support.
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > We are however still struggling to find someone with good Maven
>> >> >>> skills who is willing to help us with that task.
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > So if anyone out there is good with Maven and has the time and
>> will
>> >> >>> to support us, we would very much appreciate to hear from you.
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > Rainer
>> >> >>> >
>> >> >>> >
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> http://www.somatik.be
>> >> >>> Microsoft gives you windows, Linux gives you the whole house.
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > http://www.somatik.be
>> >> > Microsoft gives you windows, Linux gives you the whole house.
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://www.somatik.be
>> >> Microsoft gives you windows, Linux gives you the whole house.
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

What I mean by maven support is that we want users to be able to build the distribution files (i.e. apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating in http://www.apache.org/dist/incubator/empire-db) with Maven.
Also it should provide projects files for Eclipse, Net Beans etc. if possible so that we don't have to supply them with the distribution.

The build.xml Ant file supplied with the distribution could possibly remain and still work (giving the user an option).

We don't need Maven for our own development or to build the distribution.
(Unless you can convince us that it's worthwhile)

Is that how you understood it?

Regards,
Rainer


Francis De Brabandere wrote:
> Betreff: Re: Maven support for the upcoming 2.0.5 release
> 
> Do I understand correctly that you want to start building the project
> using maven instead of ant? Because you are talking about maven
> 'support'...
> 
> On Thu, Nov 13, 2008 at 12:54 PM, Rainer Döbele <do...@esteam.de> wrote:
> > Thanks a lot Francis,
> >
> > I have submitted all my recent changes and I have no local changes left.
> > Matt and Manuel should not have local changes as far as I know.
> >
> > There is one JIRA task still open from Jörg (EMPIREDB-27).
> > Jörg can you please tell us whether or not you are currently working on
> this issue?
> >
> > I have created a new JIRA-Task for the MAVEN support.
> > See https://issues.apache.org/jira/browse/EMPIREDB-29
> > Please use EMPIREDB-29 in your comment when you check in modified files.
> >
> > Regards,
> > Rainer
> >
> > Francis De Brabandere wrote:
> >>
> >> Is there a lot of activity in subversion at the moment? The switch
> >> should take about an evening of work (CET (UTC+1)). Are there any
> >> active branches?
> >> I'm willing to set everything up but you need to make sure nobody has
> >> local modifications since everything is going to be moved.
> >>
> >> Francis
> >>
> >> On Tue, Nov 11, 2008 at 12:22 PM, Francis De Brabandere
> >> <fr...@gmail.com> wrote:
> >> > Hi,
> >> >
> >> > The first step for moving to maven is always moving everything into
> >> > the maven layout and updating the ant scripts. This if you want a
> >> > gradual migration.
> >> > http://maven.apache.org/guides/introduction/introduction-to-the-
> >> standard-directory-layout.html
> >> >
> >> > I suppose there will be one parent module, one main empire-db module,
> >> > the struts integration module and some example modules
> >> >
> >> > Regards,
> >> >
> >> > Francis
> >> >
> >> > On Tue, Nov 11, 2008 at 11:48 AM, Jörg Reiher <re...@esteam.de>
> wrote:
> >> >> Hi Francis,
> >> >> first thanks for reporting the bug in the SampleConfig - that's
> >> definitely a good start to contribute :-)!
> >> >>
> >> >> As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5
> of
> >> struts extension respectively) should be to "mavenize" the empire-db
> >> source code.
> >> >> This doesn't require deep insight into empire-db, but a good
> knowledge
> >> of Maven. So if you feel comfortable with Maven (or you want to get
> >> comfortable :-) then this would be great.
> >> >> To start I'd look into other Apache (Incubator) projects to see how
> >> they used Maven. By "mavenizing" empire-db we could get rid of some
> >> dependencies and we'd overcome the trouble with
> >> >> proprietary db drivers, because the user could download them from
> the
> >> Maven repository (we can't provide proprietary drivers in the Apache
> svn
> >> of course).
> >> >>
> >> >> There are a lot of other things that could be done for empire-db
> that
> >> need some more insight into the code, for example:
> >> >> - Implementing drivers for other databases (DerbyDB comes to mind as
> >> it's also an Apache project)
> >> >> -> a starting point would be to take a closer look at the *Driver*
> >> classes in the empire-db project, maybe even starting with a copy of
> one
> >> of these as a "template"
> >> >> - Searching and reporting bugs and/or improvements
> >> >> - Creating "extensions" for other web/gui frameworks to leverage the
> >> meta data provided by empire-db
> >> >> -> this is of course quite time consuming and needs quite good
> >> knowledge of the empire-db components and the targeted web/gui
> framework
> >> >>
> >> >> So far,
> >> >> I hope I could help a little bit
> >> >> any contribution and questions are welcome,
> >> >> so don't hesitate to post it here
> >> >>
> >> >> Greetings
> >> >> jorg
> >> >>
> >> >>> -----Ursprüngliche Nachricht-----
> >> >>> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
> >> >>> Gesendet: Sonntag, 9. November 2008 17:20
> >> >>> An: empire-db-user@incubator.apache.org
> >> >>> Cc: empire-db-dev@incubator.apache.org
> >> >>> Betreff: Re: Maven support for the upcoming 2.0.5 release
> >> >>>
> >> >>> I might be willing to help out but I have not even tried empire-db
> >> >>> yet... What kind of skills are you looking for?
> >> >>>
> >> >>> Regards
> >> >>>
> >> >>> Francis
> >> >>>
> >> >>> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
> >> >>> wrote:
> >> >>> > For the upcoming Empire-db 2.0.5. release we plan to provide
> Maven
> >> >>> support.
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > We are however still struggling to find someone with good Maven
> >> >>> skills who is willing to help us with that task.
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > So if anyone out there is good with Maven and has the time and
> will
> >> >>> to support us, we would very much appreciate to hear from you.
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> > Rainer
> >> >>> >
> >> >>> >
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> http://www.somatik.be
> >> >>> Microsoft gives you windows, Linux gives you the whole house.
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > http://www.somatik.be
> >> > Microsoft gives you windows, Linux gives you the whole house.
> >> >
> >>
> >>
> >>
> >> --
> >> http://www.somatik.be
> >> Microsoft gives you windows, Linux gives you the whole house.
> >
> 
> 
> 
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

Do I understand correctly that you want to start building the project
using maven instead of ant? Because you are talking about maven
'support'...

On Thu, Nov 13, 2008 at 12:54 PM, Rainer Döbele <do...@esteam.de> wrote:
> Thanks a lot Francis,
>
> I have submitted all my recent changes and I have no local changes left.
> Matt and Manuel should not have local changes as far as I know.
>
> There is one JIRA task still open from Jörg (EMPIREDB-27).
> Jörg can you please tell us whether or not you are currently working on this issue?
>
> I have created a new JIRA-Task for the MAVEN support.
> See https://issues.apache.org/jira/browse/EMPIREDB-29
> Please use EMPIREDB-29 in your comment when you check in modified files.
>
> Regards,
> Rainer
>
> Francis De Brabandere wrote:
>>
>> Is there a lot of activity in subversion at the moment? The switch
>> should take about an evening of work (CET (UTC+1)). Are there any
>> active branches?
>> I'm willing to set everything up but you need to make sure nobody has
>> local modifications since everything is going to be moved.
>>
>> Francis
>>
>> On Tue, Nov 11, 2008 at 12:22 PM, Francis De Brabandere
>> <fr...@gmail.com> wrote:
>> > Hi,
>> >
>> > The first step for moving to maven is always moving everything into
>> > the maven layout and updating the ant scripts. This if you want a
>> > gradual migration.
>> > http://maven.apache.org/guides/introduction/introduction-to-the-
>> standard-directory-layout.html
>> >
>> > I suppose there will be one parent module, one main empire-db module,
>> > the struts integration module and some example modules
>> >
>> > Regards,
>> >
>> > Francis
>> >
>> > On Tue, Nov 11, 2008 at 11:48 AM, Jörg Reiher <re...@esteam.de> wrote:
>> >> Hi Francis,
>> >> first thanks for reporting the bug in the SampleConfig - that's
>> definitely a good start to contribute :-)!
>> >>
>> >> As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5 of
>> struts extension respectively) should be to "mavenize" the empire-db
>> source code.
>> >> This doesn't require deep insight into empire-db, but a good knowledge
>> of Maven. So if you feel comfortable with Maven (or you want to get
>> comfortable :-) then this would be great.
>> >> To start I'd look into other Apache (Incubator) projects to see how
>> they used Maven. By "mavenizing" empire-db we could get rid of some
>> dependencies and we'd overcome the trouble with
>> >> proprietary db drivers, because the user could download them from the
>> Maven repository (we can't provide proprietary drivers in the Apache svn
>> of course).
>> >>
>> >> There are a lot of other things that could be done for empire-db that
>> need some more insight into the code, for example:
>> >> - Implementing drivers for other databases (DerbyDB comes to mind as
>> it's also an Apache project)
>> >> -> a starting point would be to take a closer look at the *Driver*
>> classes in the empire-db project, maybe even starting with a copy of one
>> of these as a "template"
>> >> - Searching and reporting bugs and/or improvements
>> >> - Creating "extensions" for other web/gui frameworks to leverage the
>> meta data provided by empire-db
>> >> -> this is of course quite time consuming and needs quite good
>> knowledge of the empire-db components and the targeted web/gui framework
>> >>
>> >> So far,
>> >> I hope I could help a little bit
>> >> any contribution and questions are welcome,
>> >> so don't hesitate to post it here
>> >>
>> >> Greetings
>> >> jorg
>> >>
>> >>> -----Ursprüngliche Nachricht-----
>> >>> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
>> >>> Gesendet: Sonntag, 9. November 2008 17:20
>> >>> An: empire-db-user@incubator.apache.org
>> >>> Cc: empire-db-dev@incubator.apache.org
>> >>> Betreff: Re: Maven support for the upcoming 2.0.5 release
>> >>>
>> >>> I might be willing to help out but I have not even tried empire-db
>> >>> yet... What kind of skills are you looking for?
>> >>>
>> >>> Regards
>> >>>
>> >>> Francis
>> >>>
>> >>> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
>> >>> wrote:
>> >>> > For the upcoming Empire-db 2.0.5. release we plan to provide Maven
>> >>> support.
>> >>> >
>> >>> >
>> >>> >
>> >>> > We are however still struggling to find someone with good Maven
>> >>> skills who is willing to help us with that task.
>> >>> >
>> >>> >
>> >>> >
>> >>> > So if anyone out there is good with Maven and has the time and will
>> >>> to support us, we would very much appreciate to hear from you.
>> >>> >
>> >>> >
>> >>> >
>> >>> > Rainer
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> http://www.somatik.be
>> >>> Microsoft gives you windows, Linux gives you the whole house.
>> >>
>> >
>> >
>> >
>> > --
>> > http://www.somatik.be
>> > Microsoft gives you windows, Linux gives you the whole house.
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Thanks a lot Francis,

I have submitted all my recent changes and I have no local changes left.
Matt and Manuel should not have local changes as far as I know.

There is one JIRA task still open from Jörg (EMPIREDB-27).
Jörg can you please tell us whether or not you are currently working on this issue?

I have created a new JIRA-Task for the MAVEN support.
See https://issues.apache.org/jira/browse/EMPIREDB-29
Please use EMPIREDB-29 in your comment when you check in modified files.

Regards,
Rainer

Francis De Brabandere wrote:
> 
> Is there a lot of activity in subversion at the moment? The switch
> should take about an evening of work (CET (UTC+1)). Are there any
> active branches?
> I'm willing to set everything up but you need to make sure nobody has
> local modifications since everything is going to be moved.
> 
> Francis
> 
> On Tue, Nov 11, 2008 at 12:22 PM, Francis De Brabandere
> <fr...@gmail.com> wrote:
> > Hi,
> >
> > The first step for moving to maven is always moving everything into
> > the maven layout and updating the ant scripts. This if you want a
> > gradual migration.
> > http://maven.apache.org/guides/introduction/introduction-to-the-
> standard-directory-layout.html
> >
> > I suppose there will be one parent module, one main empire-db module,
> > the struts integration module and some example modules
> >
> > Regards,
> >
> > Francis
> >
> > On Tue, Nov 11, 2008 at 11:48 AM, Jörg Reiher <re...@esteam.de> wrote:
> >> Hi Francis,
> >> first thanks for reporting the bug in the SampleConfig - that's
> definitely a good start to contribute :-)!
> >>
> >> As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5 of
> struts extension respectively) should be to "mavenize" the empire-db
> source code.
> >> This doesn't require deep insight into empire-db, but a good knowledge
> of Maven. So if you feel comfortable with Maven (or you want to get
> comfortable :-) then this would be great.
> >> To start I'd look into other Apache (Incubator) projects to see how
> they used Maven. By "mavenizing" empire-db we could get rid of some
> dependencies and we'd overcome the trouble with
> >> proprietary db drivers, because the user could download them from the
> Maven repository (we can't provide proprietary drivers in the Apache svn
> of course).
> >>
> >> There are a lot of other things that could be done for empire-db that
> need some more insight into the code, for example:
> >> - Implementing drivers for other databases (DerbyDB comes to mind as
> it's also an Apache project)
> >> -> a starting point would be to take a closer look at the *Driver*
> classes in the empire-db project, maybe even starting with a copy of one
> of these as a "template"
> >> - Searching and reporting bugs and/or improvements
> >> - Creating "extensions" for other web/gui frameworks to leverage the
> meta data provided by empire-db
> >> -> this is of course quite time consuming and needs quite good
> knowledge of the empire-db components and the targeted web/gui framework
> >>
> >> So far,
> >> I hope I could help a little bit
> >> any contribution and questions are welcome,
> >> so don't hesitate to post it here
> >>
> >> Greetings
> >> jorg
> >>
> >>> -----Ursprüngliche Nachricht-----
> >>> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
> >>> Gesendet: Sonntag, 9. November 2008 17:20
> >>> An: empire-db-user@incubator.apache.org
> >>> Cc: empire-db-dev@incubator.apache.org
> >>> Betreff: Re: Maven support for the upcoming 2.0.5 release
> >>>
> >>> I might be willing to help out but I have not even tried empire-db
> >>> yet... What kind of skills are you looking for?
> >>>
> >>> Regards
> >>>
> >>> Francis
> >>>
> >>> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
> >>> wrote:
> >>> > For the upcoming Empire-db 2.0.5. release we plan to provide Maven
> >>> support.
> >>> >
> >>> >
> >>> >
> >>> > We are however still struggling to find someone with good Maven
> >>> skills who is willing to help us with that task.
> >>> >
> >>> >
> >>> >
> >>> > So if anyone out there is good with Maven and has the time and will
> >>> to support us, we would very much appreciate to hear from you.
> >>> >
> >>> >
> >>> >
> >>> > Rainer
> >>> >
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> http://www.somatik.be
> >>> Microsoft gives you windows, Linux gives you the whole house.
> >>
> >
> >
> >
> > --
> > http://www.somatik.be
> > Microsoft gives you windows, Linux gives you the whole house.
> >
> 
> 
> 
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Martijn Dashorst <ma...@gmail.com>]

The best way to adopt maven is to adopt its best practices, which
include shuffling around directories, you and your users will thank
you for that. Any bad experience with maven is 99% of the cases
someone fighting maven instead of embracing it.

Martijn

On Thu, Nov 13, 2008 at 1:13 PM, Rainer Döbele <do...@esteam.de> wrote:
> Hi Francis,
>
> one more thing before you start: It would be good if the project structure as it is currently in Subversion would not change and if the Ant scripts would still work.
>
> IMO the projects structure should be suitable since it is similar to most Apache projects. As you have probably already seen, we have two distribution packages which are in the trunk: core (Empire-db) and struts2-ext (Empire-Struts2-ext). We are currently preparing our distributions using the buildRelease.xml Ant Scripts.
>
> If there is anything major that would mix up the whole project layout I would appreciate if you could give us a brief explanation about what needs to be done and what the effects would be.
>
> Regards
> Rainer
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.4 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

Maven support for the upcoming 2.0.5 release

[Rainer Döbele <do...@esteam.de>]

Hi Francis,

one more thing before you start: It would be good if the project structure as it is currently in Subversion would not change and if the Ant scripts would still work.

IMO the projects structure should be suitable since it is similar to most Apache projects. As you have probably already seen, we have two distribution packages which are in the trunk: core (Empire-db) and struts2-ext (Empire-Struts2-ext). We are currently preparing our distributions using the buildRelease.xml Ant Scripts.

If there is anything major that would mix up the whole project layout I would appreciate if you could give us a brief explanation about what needs to be done and what the effects would be.

Regards
Rainer

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

Is there a lot of activity in subversion at the moment? The switch
should take about an evening of work (CET (UTC+1)). Are there any
active branches?
I'm willing to set everything up but you need to make sure nobody has
local modifications since everything is going to be moved.

Francis

On Tue, Nov 11, 2008 at 12:22 PM, Francis De Brabandere
<fr...@gmail.com> wrote:
> Hi,
>
> The first step for moving to maven is always moving everything into
> the maven layout and updating the ant scripts. This if you want a
> gradual migration.
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>
> I suppose there will be one parent module, one main empire-db module,
> the struts integration module and some example modules
>
> Regards,
>
> Francis
>
> On Tue, Nov 11, 2008 at 11:48 AM, Jörg Reiher <re...@esteam.de> wrote:
>> Hi Francis,
>> first thanks for reporting the bug in the SampleConfig - that's definitely a good start to contribute :-)!
>>
>> As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5 of struts extension respectively) should be to "mavenize" the empire-db source code.
>> This doesn't require deep insight into empire-db, but a good knowledge of Maven. So if you feel comfortable with Maven (or you want to get comfortable :-) then this would be great.
>> To start I'd look into other Apache (Incubator) projects to see how they used Maven. By "mavenizing" empire-db we could get rid of some dependencies and we'd overcome the trouble with
>> proprietary db drivers, because the user could download them from the Maven repository (we can't provide proprietary drivers in the Apache svn of course).
>>
>> There are a lot of other things that could be done for empire-db that need some more insight into the code, for example:
>> - Implementing drivers for other databases (DerbyDB comes to mind as it's also an Apache project)
>> -> a starting point would be to take a closer look at the *Driver* classes in the empire-db project, maybe even starting with a copy of one of these as a "template"
>> - Searching and reporting bugs and/or improvements
>> - Creating "extensions" for other web/gui frameworks to leverage the meta data provided by empire-db
>> -> this is of course quite time consuming and needs quite good knowledge of the empire-db components and the targeted web/gui framework
>>
>> So far,
>> I hope I could help a little bit
>> any contribution and questions are welcome,
>> so don't hesitate to post it here
>>
>> Greetings
>> jorg
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
>>> Gesendet: Sonntag, 9. November 2008 17:20
>>> An: empire-db-user@incubator.apache.org
>>> Cc: empire-db-dev@incubator.apache.org
>>> Betreff: Re: Maven support for the upcoming 2.0.5 release
>>>
>>> I might be willing to help out but I have not even tried empire-db
>>> yet... What kind of skills are you looking for?
>>>
>>> Regards
>>>
>>> Francis
>>>
>>> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
>>> wrote:
>>> > For the upcoming Empire-db 2.0.5. release we plan to provide Maven
>>> support.
>>> >
>>> >
>>> >
>>> > We are however still struggling to find someone with good Maven
>>> skills who is willing to help us with that task.
>>> >
>>> >
>>> >
>>> > So if anyone out there is good with Maven and has the time and will
>>> to support us, we would very much appreciate to hear from you.
>>> >
>>> >
>>> >
>>> > Rainer
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> http://www.somatik.be
>>> Microsoft gives you windows, Linux gives you the whole house.
>>
>
>
>
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

Hi,

The first step for moving to maven is always moving everything into
the maven layout and updating the ant scripts. This if you want a
gradual migration.
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html

I suppose there will be one parent module, one main empire-db module,
the struts integration module and some example modules

Regards,

Francis

On Tue, Nov 11, 2008 at 11:48 AM, Jörg Reiher <re...@esteam.de> wrote:
> Hi Francis,
> first thanks for reporting the bug in the SampleConfig - that's definitely a good start to contribute :-)!
>
> As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5 of struts extension respectively) should be to "mavenize" the empire-db source code.
> This doesn't require deep insight into empire-db, but a good knowledge of Maven. So if you feel comfortable with Maven (or you want to get comfortable :-) then this would be great.
> To start I'd look into other Apache (Incubator) projects to see how they used Maven. By "mavenizing" empire-db we could get rid of some dependencies and we'd overcome the trouble with
> proprietary db drivers, because the user could download them from the Maven repository (we can't provide proprietary drivers in the Apache svn of course).
>
> There are a lot of other things that could be done for empire-db that need some more insight into the code, for example:
> - Implementing drivers for other databases (DerbyDB comes to mind as it's also an Apache project)
> -> a starting point would be to take a closer look at the *Driver* classes in the empire-db project, maybe even starting with a copy of one of these as a "template"
> - Searching and reporting bugs and/or improvements
> - Creating "extensions" for other web/gui frameworks to leverage the meta data provided by empire-db
> -> this is of course quite time consuming and needs quite good knowledge of the empire-db components and the targeted web/gui framework
>
> So far,
> I hope I could help a little bit
> any contribution and questions are welcome,
> so don't hesitate to post it here
>
> Greetings
> jorg
>
>> -----Ursprüngliche Nachricht-----
>> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
>> Gesendet: Sonntag, 9. November 2008 17:20
>> An: empire-db-user@incubator.apache.org
>> Cc: empire-db-dev@incubator.apache.org
>> Betreff: Re: Maven support for the upcoming 2.0.5 release
>>
>> I might be willing to help out but I have not even tried empire-db
>> yet... What kind of skills are you looking for?
>>
>> Regards
>>
>> Francis
>>
>> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
>> wrote:
>> > For the upcoming Empire-db 2.0.5. release we plan to provide Maven
>> support.
>> >
>> >
>> >
>> > We are however still struggling to find someone with good Maven
>> skills who is willing to help us with that task.
>> >
>> >
>> >
>> > So if anyone out there is good with Maven and has the time and will
>> to support us, we would very much appreciate to hear from you.
>> >
>> >
>> >
>> > Rainer
>> >
>> >
>>
>>
>>
>> --
>> http://www.somatik.be
>> Microsoft gives you windows, Linux gives you the whole house.
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

AW: Maven support for the upcoming 2.0.5 release

[Jörg Reiher <re...@esteam.de>]

Hi Francis,
first thanks for reporting the bug in the SampleConfig - that's definitely a good start to contribute :-)!

As Rainer already stated, the main goal for release 2.0.5 (and 1.0.5 of struts extension respectively) should be to "mavenize" the empire-db source code.
This doesn't require deep insight into empire-db, but a good knowledge of Maven. So if you feel comfortable with Maven (or you want to get comfortable :-) then this would be great.
To start I'd look into other Apache (Incubator) projects to see how they used Maven. By "mavenizing" empire-db we could get rid of some dependencies and we'd overcome the trouble with
proprietary db drivers, because the user could download them from the Maven repository (we can't provide proprietary drivers in the Apache svn of course).

There are a lot of other things that could be done for empire-db that need some more insight into the code, for example:
- Implementing drivers for other databases (DerbyDB comes to mind as it's also an Apache project)
-> a starting point would be to take a closer look at the *Driver* classes in the empire-db project, maybe even starting with a copy of one of these as a "template"
- Searching and reporting bugs and/or improvements
- Creating "extensions" for other web/gui frameworks to leverage the meta data provided by empire-db
-> this is of course quite time consuming and needs quite good knowledge of the empire-db components and the targeted web/gui framework

So far,
I hope I could help a little bit
any contribution and questions are welcome,
so don't hesitate to post it here

Greetings
jorg

> -----Ursprüngliche Nachricht-----
> Von: Francis De Brabandere [mailto:francisdb@gmail.com]
> Gesendet: Sonntag, 9. November 2008 17:20
> An: empire-db-user@incubator.apache.org
> Cc: empire-db-dev@incubator.apache.org
> Betreff: Re: Maven support for the upcoming 2.0.5 release
> 
> I might be willing to help out but I have not even tried empire-db
> yet... What kind of skills are you looking for?
> 
> Regards
> 
> Francis
> 
> On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de>
> wrote:
> > For the upcoming Empire-db 2.0.5. release we plan to provide Maven
> support.
> >
> >
> >
> > We are however still struggling to find someone with good Maven
> skills who is willing to help us with that task.
> >
> >
> >
> > So if anyone out there is good with Maven and has the time and will
> to support us, we would very much appreciate to hear from you.
> >
> >
> >
> > Rainer
> >
> >
> 
> 
> 
> --
> http://www.somatik.be
> Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

I might be willing to help out but I have not even tried empire-db
yet... What kind of skills are you looking for?

Regards

Francis

On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de> wrote:
> For the upcoming Empire-db 2.0.5. release we plan to provide Maven support.
>
>
>
> We are however still struggling to find someone with good Maven skills who is willing to help us with that task.
>
>
>
> So if anyone out there is good with Maven and has the time and will to support us, we would very much appreciate to hear from you.
>
>
>
> Rainer
>
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Re: Maven support for the upcoming 2.0.5 release

[Francis De Brabandere <fr...@gmail.com>]

I might be willing to help out but I have not even tried empire-db
yet... What kind of skills are you looking for?

Regards

Francis

On Sun, Nov 9, 2008 at 12:34 PM, Rainer Döbele <do...@esteam.de> wrote:
> For the upcoming Empire-db 2.0.5. release we plan to provide Maven support.
>
>
>
> We are however still struggling to find someone with good Maven skills who is willing to help us with that task.
>
>
>
> So if anyone out there is good with Maven and has the time and will to support us, we would very much appreciate to hear from you.
>
>
>
> Rainer
>
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.