continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Whitlock" <>
Subject MRELEASE-130 Progress
Date Sat, 26 Aug 2006 02:02:48 GMT
Hi All,
    I started working on this today and I have run into a few things that I
would like you to be aware of just in case you have a better way of handling
the situation.

As I was going through and creating the modello for ReleaseDescriptor, used
to replace the ReleaseConfiguration, I ran into an issue where some of the
things that are currently stored in the ReleaseConfiguration, but not
necessarily persisted to the release properties file, that cannot be stored
in a modello file.  I have done some researching and I do think that these
items do not necessarily need to be in the ReleaseDescriptor.  The problem
is that the release plugin still needs to get access to these things, like
the Settings object, to perform the release.  That being said, my plan is to
refactor and pass these objects to the proper methods where they are needed
and not worry about storing them in the ReleaseDescriptor.  Does anyone see
any problem with this or have any suggestions in the matter?

Take care,


P.S. - To see what I am speaking of, open the "
org.apache.maven.plugins.release.config.ReleaseConfiguration" file and look
at all local member variables that are not capable of being stored in a
class created by modello.  (For example: The Settings, List and Map
objects)  If you have time, look at how they are used and get back to me.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message