Re: [ginp-users] Subversion and Maven

[Doug C. <do...@cu...>]

You can subscribe to the developers list without restrictions.  Move
discussion to this list.

Looks like the URL may have changed.

Will get back to you on commit access.

I only work on the trunk.

Agree with the Maven Only build, for now it is much less work.

The log4J WARN is not an error.  You can set the environment variable
"log4j.configuration" to point to you log4j config file to get loggin
output.  (Search for log4j.configuration on
http://logging.apache.org/log4j/docs/manual.html  for more info.)

To get a build skip tests
> mvn install -Dmaven.test.skip=true

Find out what test fails:
> mvn site
Browse the HTML site in ./target/site/  for surefire results and you
will get test failure info.
(see: http://ginp.sourceforge.net/surefire-report.html)

All the best,

Doug


Brian Burch wrote:
> Doug, Happy New Year!
>
> I've finally found a few hours to start learning subversion (I have it 
> working under netbeans) and maven (working standalone-only so far).
>   
>> Subversion is very much like cvs. You will need a new client program or
>> plugin because a cvs client does not work with subversion server. I use
>> command line cvs and svn commands and they are very similar. The
>> learning cure here will be small. CVS will no longer be used for the
>> source code.
>>
>> # quick howto
>>
>> svn co http://svn.sorceforge.net/svnroot/ginp/trunk ginp
>>     
>
> Is this still correct? I had to configure subversion-netbeans with:
>
> url - http://ginp.svn.sorceforge.net/svnroot/ginp
> folder - trunk
> repository revision - (empty for HEAD)
>
>   
>> You can send me patches and files or if you get sorted out with
>> subversion I will let you commit directly.
>>
>>     
>
> Would you please add me to the list of project developers? This will 
> allow me to email the developers mailing list in cases where it is more 
> appropriate than the users list. My sourceforge userid is "burchbri".
>
> If it is simpler for you, please also add me to the committers list at 
> the same time - I promise not to commit any changes until either agreed 
> first with you, or trivial.
>
>   
>> I will be using maven not ant because Maven has various project
>> management advantages that are complex to script with ant. However it
>> would be great to have an ant build file that built the project, so if
>> you would like to contribute this it would be great. The only problem is
>> that I no longer have the libs in the source code repository. They are
>> downloaded by maven. The ant build would also need to get this files or
>> have a documentation informing the developer to download the following
>> dependencies.... Not sure how best to solve this.
>>
>>     
>
> I have maven installed and working. I've done a couple of tutorials and 
> some other research. I am not sure it is worth the effort of creating 
> and maintaining a parallel ant build.xml file. My own opinion is that it 
> would create confusion (what tool to use?) and should be removed 
> completely from the source repository as soon as you are certain the 
> maven goals build exactly as you intend. If anyone wants to build from 
> source (e.g. me), it must be done with maven (or not at all).
>
>   
>> I have investigated logging at work a bit I and I think commons logging
>> with a log4j implementation is the best way to go. Commons logging is
>> like a interface that most popular loggers implement, including my
>> favorite log4j. I will do some work and documentation on this. If you
>> are interested read: http://jakarta.apache.org/commons/logging/ Apache
>> also have the logging services project which also used log4j but
>> directly. Again I am not totally sure about the best approach but I
>> think commons logging is the most flexible.
>>
>>     
>
> I ran "mvn compile" successfully. However, the "test" and "install" 
> goals both fail in the "test" stage of the project life cycle.
>
> log4j: WARN No appenders could be found for logger 
> (net.sf.ginp.config.Configuration)
> log4j: WARN Please initialize the log4j system properly.
>
> This is a variation on our previously-fixed log4j problems. If you 
> haven't already resolved it in one of your branch builds, let me know 
> (soon) and I'll sort it out. Until it is fixed, maven will not succeed 
> with the tests and move on to the next (package?) goal.
>
>   
>> I am working on the subversion truck (no tags or branches yet) If you
>> want the best jet version of ginp then download the released source zip
>> file. It may take me a while to get the source version back to a
>> reasonable quality level. However if you find a bug with it then please
>> let me known.
>>
>>     
>
> Are you still working on the trunk, or one of the 3 branches? I assumed 
> my future log4j change would go to the trunk.
>
>  > Thanks for the https info I will try to get round and test this.
>  >
>
> Did you try? If not, I'll have a go as soon as I can get a clean maven 
> build.
>
> Regards,
>
> Brian
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> ginp-users mailing list
> gin...@li...
> https://lists.sourceforge.net/lists/listinfo/ginp-users
>