Re: [Maven-plugins-developer] [Maven-plugins-user] Publishedjavaapp-1.4-snapshot

[Jeff J. <jef...@up...>]

=20

> -----Original Message-----
> From: mav...@li...=20
> [mailto:mav...@li...]
>  On Behalf Of J=F6rg Schaible
> Sent: Monday, July 31, 2006 8:25 AM
> To: mav...@li...
> Subject: Re: [Maven-plugins-developer] [Maven-plugins-user]=20
> Publishedjavaapp-1.4-snapshot
>=20
> Hi Jeff,
>=20
> Jeff Jensen wrote on Monday, July 31, 2006 2:57 PM:
>=20
> > Hi J=F6rg,
> >=20
> > Eclipse files: Because other plugins have the Eclipse=20
> files, they are=20
> > source-config files, and I found it convenient when they=20
> were already=20
> > there so I added them to the projects I setup to fix things on.
>=20
> Since you generate them normally with Maven anyway, I find it=20
> normally quite scary, if I have suddenly conflicts updating a=20
> project. Especially if it includes settings that may not=20
> match my preferences ;-)
>=20
> But it might be a mood point for javaapp, since meanwhile I=20
> switched to M2 also any my motivation to maintain M1 plugins=20
> has been .


That's a good point.  I don't use the maven eclipse plugin, so that =
would be
why!  :-)  With the various projects I work on, and my customers' work, =
we
always source-control the IDE config files too.  So it is also a habit!

No one else has been working on these SF plugins for about a year, so I =
also
didn't expect anyone to care!  :-)

If they are bothersome, we can consider deleting them.


> > Version num: Because I just bumped the rev since I'm not sure what=20
> > else is going into the releases yet.  I have been applying some=20
> > patches and trying to fix some issues to eliminate the ancient=20
> > backlog!  If others such as yourself will take the plugin version=20
> > numbers quite seriously, then I will do the sub-point=20
> release approach=20
> > in the future.
>=20
> I released 1.3.1 also from 1.4-SNAPSHOT. As long as it just=20
> contains bug fixes without any new functionality or=20
> incompatible changes, it might be the better approach.

Certainly.  Will respect that traditional approach again.  It was also =
part
of the "I didn't expect anyone to care".  ;-)


> > Keeping track of added issues: Recently I changed all SF=20
> trackers to=20
> > email changes to the dev list.  This will make it easier=20
> for us to see=20
> > them vs continually polling.
>=20
> Fine. That always annoyed me. I catched some entries=20
> regarding javaapp, but I had to admin that I did not check=20
> the entries in the last months ... so thanks for taking up=20
> the torch :)

For a few plugins that I have particularly maintained, there were 2 =
defects
logged at the beginning of July, and I just found them the other day.  I
passionately hate that kind of poor response!  I had configured the =
maillist
sending before that, but for some reason not all emails made it through.
They seem to come through correctly now though.  Not sure what changed.



Thanks for your input/concerns/replies.  Nice to know others will =
monitor
and care about these still!

Even though you have moved on to M2, any expertise you can provide on
applying any of the patches in the Patches and/or Bugs trackers would be
very helpful.  Some of them I can't process easily/quickly due to lack =
of
understanding the plugin (I have not used most of these!), so they =
become
longer to process and slower for me to get to.  And I hesitate as well, =
as I
would rather not break something more!=20